Quantcast
Channel: LabVIEW topics
Viewing all articles
Browse latest Browse all 69439

Project properties: Separate Compiled code?

$
0
0

I'm refactoring some code from LabVIEW 8.5 to LabVIEW 2013 SP1 with the intent of creating an executable with an installer.

I tried to create an executable from my project and when I ran it I got a bunch of Error code 59: The source file's compiled code has been seperated, and this version of LabVIEW does not have access to seperated compiled code. It turns out that for many of the NI RGT and Office toolkit vi's the checkmark is set by default to seperate the compiled code. 

 

The question is that if I unset the checkmark in the project properties window will this carry over to the subvi's in the project or must I unset the checkmark for every vi used in the project? If I click on the 'Mark Existing Items...' button and set the status to unmarked (the file uses the closed folder glyph) will that perform the needed action of including compiled code for every vi in the project?

 

 


Viewing all articles
Browse latest Browse all 69439

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>