How to use build exclusions on certain functions?

Question

Hi all, I just attended the GDVC breakout session about optimal Monkey C. Thank you, Garmin for adding the option to type check! I think type checking can help me find code I'm not using and get rid of it. When I turn type checking on though, I get errors about undefined symbols for this code (simplified). Would you all mind taking a look and giving me tips on how I can get this to work?

//...
if (id == :item_15) { 
 // this menu option only pops up if routing is enabled for the device. 
 // But the compiler doesn't know that, and when I run a device that
 // doesn't support routing, I get this error:
 // Undefined symbol ':request_directions_to_pin' detected.
 request_directions_to_pin();
} else if (id == :item_16) {
 do_other_things();
}
//...


(:routing)
function request_directions_to_pin() {
 // do stuff
} 
 
 Thanks!

flowstate · Answer

One approach is to have a pair of exclusions for every feature you want to "conditionally compile" in this manner, which can get annoying to maintain in your jungle file, as you can imagine. 
 It can help to define a default set of exclusions, and explicitly assign other sets of exclusions to devices which are the exception to the rule. 
 e.g. Let's pretend out of all the devices you build for, only FR 955 supports routing and hrv . (I'm making up a new feature for your app for the purposes of this example) 
 monkey.jungle: 
 # The following exclude annotations are applied by default base.excludeAnnotations = routing;hrv # List all the exceptions to the default rule here fr955.excludeAnnotations = no_routing;no_hrv # ... 
 app source: 
 (:routing) function request_directions_to_pin() { // do stuff // ... } 
 (:no_routing) function request_directions_to_pin() { } 
 (:hrv) function get_hrv_sensor_data() { // get data // ... return data; } 
 (:no_hrv) function get_hrv_sensor_data() { return null; } 
 You'll notice that if memory is a concern here, your empty functions and the code that calls them still take up memory in the form of code. It's not much, but it can be an issue for data fields on older devices or even current devices such as vivoactive 4.

How to use build exclusions on certain functions?

Top Replies

All Replies