Jump to content

Recommended Posts

I use several conditional disable symbols in my project. I'd like to create a build script for each spec that sets the symbols to a value appropriate for that build. Is there a way to retrieve the symbol names and values using scripting or vi server? This is as far as I got when I realized I have no idea how to proceed...

post-7603-044736200 1288885694_thumb.png

Share this post


Link to post
Share on other sites

I use several conditional disable symbols in my project. I'd like to create a build script for each spec that sets the symbols to a value appropriate for that build. Is there a way to retrieve the symbol names and values using scripting or vi server? This is as far as I got when I realized I have no idea how to proceed...

I've been meaning to post this:

I've been working on "LabVIEW Project.lvlib" but it's not really ready for prime time. Would be good to have some collaboration.

Modify Conditional Symbol.vi

Share this post


Link to post
Share on other sites

I couldn't open the other example since I'm still on 8.6, but here's a quick example that I banged out a while ago for a team mate and was still on my desktop.

Well evidently I'm not permitted to upload a *.lvproj file. But you should be able to add it to a project an run it.

Sample.vi

Share this post


Link to post
Share on other sites

This post is kind of old, I don't know if JGCode released his project API, so my apologies if this is already somewhere else.

 

I just wanted to add a note here in case someone else tried to use the project API.

The tags used in the build specification for the version have changed. JGCode uses inside "Executable Get Version_jgcode_lib_labview_project_api.vi" :

App_fileVersion.major

App_fileVersion.minor

App_fileVersion.patch

App_fileVersion.build

 

at least on the version I am working on now (LabVIEW 2012) the tags are:

TgtF_fileVersion.major

TgtF_fileVersion.minor

TgtF_fileVersion.patch

TgtF_fileVersion.build

 

Also, this is only useful in development mode, because as MJE showed in this post: http://lavag.org/topic/15473-getting-the-version-of-a-build-from-the-project/?p=93474

you can use that vi to extract the actual exe version at run time.

  • Like 2

Share this post


Link to post
Share on other sites

With LabVIEW 2013 and LabVIEW 2014, it seems that the tag names have changed again:

Bld_version.major
Bld_version.minor
Bld_version.patch
Bld_version.build

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.