NI Package BUILDER: Feature or Bug?

[Oli_Wachno]

Hi y'all,

[Background] we're in a transitional state between 2019 32 Bit and 2024Q3 64 Bit, so I have to maintain compatiblities..

So I have LabVIEW 2019 32 Bit Code (Compiled Code seperated) and I want to create a nipkg using NIPB. 

Spoiler

I am NOT using a NIPKG Build Script in LabVIEW, since I find the options there very intransparent (like... I can choose to use the ProgramFiles folder as Destination, but is that ProgramFiles or ProgramFiles(x86))

When I build the package, LV2024Q3 gets launched in the background and updates everything before actually building the Package, eben though LabVIEW 2019 is active and running..

To me, this doesn't make sense and renders NIPB useless for this use case. What am I missing?

Oli

[Scott_Richardson · Accepted solution]

NIPB by default tries to process LabVIEW files, I thought that LabVIEW files are only processes if called by TestStand, but I am not positive about that; have not worked on NIPB in a while

NIPB supports a per file property called "Process during staging" that when disabled it just treats it as a non-LabVIEW file. You should be able to multi-select files in the middle pane and change that property on the right.

The property has the following description:

For a TestStand sequence file, specifies whether Package Builder updates the file paths specified in the file to match the destinations of the dependencies. Refer to Processing TestStand Sequence Files for more information on how TestStand files are processed when this option is selected.

For a LabVIEW file, specifies whether Package Builder includes the file in the package without any additional processing. For example, Package Builder will not go through the process of re-saving a VI in the active version of LabVIEW. You must ensure that unprocessed LabVIEW files will work properly with LabVIEW once installed.

---

[Oli_Wachno]

Scott,

as usually: thanks so very much for the insights!
This flag did the job!

Happy Holidays!

Oli