06-10-2015 02:39 AM
I would like to build a lvlibp from a lvlib and set the build specification version number to the lvlibp version number with a pre-build action.
I tried two solutions in the pre-build action without success:
1- Read the version number of the build specification and set the version number of the lvlib by property node,
2- Read the version number of the build specification and write the version number in the xml file of the lvlib,
For each solution, the lvilb seems to be in memory as soon as the build is launched and the version is not taken into account. The version of the lvlibp is not overwritten by the build specification version number.
I don't have any error and in the 2nd solution, if I check the version number of the lvlib after the build, it's equal to the build specification version number.
Have you got a solution?
06-11-2015 09:28 AM - edited 06-11-2015 09:29 AM
Hi DMous,
Here you will find the explanations of what you are seeing :
Regards,
Valentin
Certified LabVIEW Architect
Certified TestStand Architect
Certified LabWindowsCVI Developer
National Instruments France
06-11-2015 02:51 PM
Yes, I discovered that the Pre-Build Action "grabs" the Version number first, then lets you modify it in the Project, then continues with the Build using the original Version number. I did complain, and NI basically said "That's the way we do it". Grrr ...
My "Workaround" is to Code LabVIEW Once, Build Twice (a very bad paraphrase from carpentery). During the first Build, the Pre-Build Action will update the Build Number in the Project. Immediately do another Build, during which time the Pre-Build Action will use the updated Build Number.
Does this seem as silly to you as it does to me? If so, go to my Idea Exchange post (LabVIEW Idea Exchange) and make a comment or vote for this idea,
Bob Schor