Jump to content

Programmatic Build does not update tags in Project

Recommended Posts

I am trying to get a build script going, and I use the destination folder format with the tag [VersionNumber] in the Primary Destination Path (http://digital.ni.com/public.nsf/allkb/617928B8E8DE3B6C86257CC400429194)

What is happening is that when I do my programmatic build, the lvproject only "remembers" the last build I manually did through the project itself, instead of the programmatic build.

for example, say I right click on my executable build specification, select "build".  My build will run, complete, and then all the files will be stored in the folder builds\EXE  The flag "Auto Increment" is set to True. 

Now, I run my build script 5 times.  I will have folders EXE through EXE  I open my exe build specification in the labview project, navigate to the "Version Information" page, and the Version Number correctly shows as the next build number.  So my build script is updating the build specification with the correct auto increment, and I have verified that LabVIEW is creating the correct files in the correct folder.

But, when I go to the build specification, right click and select "Explore", LabVIEW opens the EXE folder, instead of the EXE folder.

The consequence is that when I do an installer build, LabVIEW thinks that the build was the last build, so the incorrect exe is copied into the installer.

Has anyone run into this issue with programmatic builds?

build steps.PNG

Link to comment

So the main problem is getting the installer build script to get updated with the correct EXE build. I wonder if there's a way to signal that change to the installer script.

I've never seen this issue. However, I usually just programmatically run the installer build script right after the EXE build script and it works every time. Do you have the project open while doing all this?

Link to comment

Join the conversation

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

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.