LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Authors
cancel
Showing results for 
Search instead for 
Did you mean: 

Conditional Disable Symbols settable in Application Builder

Status: New

I use the conditional disable structure in my projects to turn debug options on and off.

At the moment before every build I have to go into the project properties and make sure that DEBUG variable is set to FALSE and after the build I have to change it back.

You can get around this by automating you build but an option in the build specifications would simplify this.

 

It would make life much more convenient if there were a list of the available (non-system) conditional disable symbols in the application builder dialog where the appropriate variables for the build could be set. This would also allow for a simple duplication of a build spec to have one with DEBUG=TRUE, and one with DEBUG=FALSE.

24 Comments
Member

Do you also come from a C++ background marshaul?  Personally, I could hardly live without this functionality.

I will write this up on the forums in the morning.

Member

Yes, my background is (in order of significance) embedded C, C++, and obj-C.

Proven Zealot

Setting the conditions in the appropriate project's tag, and calling it in a pre-build VI does the job.

 

It's just very inconvenient. Each combination needs a VI (or needs to be handled in the pre build VI). And the pre build VI changes the project settings. I save the project before the build (I have a popup that lets me cancel the build if the conditions are changed). If I don't my SCC will be screwed up, as several VIs where touched by changing the conditions.

 

It allows me to build 4 applications (and 4 installers) from the same code base in one go, using Build All.

Member

I did a quick writeup of my method, with attached VIs.  I'd love to see the methods you all use.

Scripting Conditional Disable Symbols (#IfDef)