10-01-2014 03:16 PM
After building and deploying code to a cRIO, I see that a huge amount of source code VIs are put onto the cRIO in addition to the *.rtexe file. What features of the code would cause these source code VIs to be needed in addtion to the executable?
I am using OOP in the code, in case that makes any difference. Thank you for your assistance.
10-01-2014 04:25 PM
If anything is dynamically called (which OO tends to do), that might be a reason it is on in the executable.
10-02-2014 12:10 PM
I am using a child class that sometimes calls a parent's accessor or method, but there are no situations where what class is used is indeterminate at runtime. Would calling a parent's accessor or method be considered a dynamic call?
10-03-2014 05:16 PM
Hi Chris_12345,
Are you "Always Including" the class in your build spec? If you are ever dynamically calling the class (which it does not sound like you are doing from what you said), then you should. If you are not dynamically calling it, then don't include it, and it shouldn't include those VIs.
10-08-2014 05:37 PM
I checked the Build Specification properties, and under Source Files, there is nothing under Always Included. However, under Source File Settings > Dependencies, I see that the dependencies are set to "Include if referenced". I don't see any way to change that. Can that be changed?