LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

how do I distribute a debug build

I sometimes need to distribute a debug build of my app instead of a release build, but the deployment tool insists on resetting the build type to release and rebuilding the executable in release mode.

The debug build helps with capturing exceptions so I get a reference into the source code.  Remote debugging needs the debug build as well.

Am I missing the obvious here, or Is there no way to distribute the debug build of an application?

Menchar
0 Kudos
Message 1 of 2
(3,471 Views)
The distribution builder assumes distribution of the final, release build of an application, but you can get around this by including the debug output file specifically (like any other file) instead of the symbolic, "Project Name Output" file item.  The only disadvantage to this is that the file will be tracked by absolute path, so if you move your project directory around, or change your output path in the Target Settings, you'll have to fix up your distribution settings.  A (somewhat hacky) way around the absolute path issue is to add the file to your project (Edit>>Add Files to Project>>All Files...); this will cause it to be tracked relative to the project.

You make a valid point about sometimes needing to debug the application on a different machine, so I encourage you to file a Product Suggestion if you feel debug distributions should be directly supported.

Hope this helps.

Mert A.
National Instruments
0 Kudos
Message 2 of 2
(3,467 Views)