Build Scripts

[Daklu]

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...

[jdunham]

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

[jgcode]

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.

Count me in too.

Attached is my LabVIEW Project API, (I've posted bits before).

Don't think its ready for prime-time either, but am happy to post as is.

Tested only with LV2009 thus far.

Cheers

-JG

jgcode_lib_labview_project_api-2.0.1-1.vip

jgcode_rsc_jgcode_library_palette-1.2-1.ogp

[Dan DeFriese]

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

[Fab]

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.

[crossrulz]

Fab, my testing concurrs with yours (LabVIEW 2011 SP1)

[joerghampel]

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