Build Package aborted due to missing items

[thomasliebenau]

I want to build a package with is related / uses NI Addons like NI FlexRIO.
When I try to build such a package VIPM aborts building and reports missing VIs or Libraries.

VIPM reports such VIs in a very different path then LabVIEW 2023 64bit shows them in files view of Project Explorer (see highlighted entries in screenshot).

Build is only successful when "Do Not Compile on Build (NotRrecommended)" is enabled

This happens with

• LV 2023 Q3 64bit
• VIPM 2023.3 Free Edition

With best regards,
Thomas Liebenau

[thomasliebenau]

After installing the package build with enabled option "Do Not Compile on Build (NotRrecommended)" it has a bad palette

in VIPM the palette is designed like this

[jimkring]

Hi Thomas. Thank you for reporting this and providing updates on your testing/findings. I believe it’s an issue with the new LVAddons feature (install location of NI Packagess) in LabVIEW.

[thomasliebenau]

Hi Jim,

ok. will there be an update for VIPM to fix this?

[jimkring]

Hi @thomasliebenau. This issue appears to impact package building in LabVIEW 2023 for packages with VIs calling toolkits installed under the C:\Program Files\NI\LVAddons location. Starting in 2023 many NI toolkits (like DAQmx) install VIs in this location. This will eventually be fixed in VIPM, but there is no ETA.

It should still be possible to build your package in an older version of LabVIEW (like 2020) if that's an option for you.

[jimkring]

@thomasliebenau I've filed a more detailed bug report here: #44

[thomasliebenau]

Hi Jim,

thanks for filing this as a "bug". I'm eagerly awaiting the solution.

best regards
Thomas

[jimkring]

Hi @thomasliebenau

We will have a new build with a possible fix available for testing soon. It appears to fix the issue for simple cases of calling DAQmx in 2023. I can share a download link once it’s available, if you’re willing to test it.

Jim

[thomasliebenau]

Hi @jimkring

I really like to support in testing.

Thomas

[jimkring]

Hi @thomasliebenau.

Great! Here is a link to beta build of VIPM 2024 Q1 f2 (build 2685):

• vipm-24.1.2685-f2beta-windows-setup.exe.zip

Thanks for your help testing this and please let us know how it works for building your package. It would be nice to close this issue :)

-Jim

[jimkring]

Hi @thomasliebenau. I saw a post flyby that seems to be gone now. it looked like there were some issues related to building packages that call FPGA add-ons.

[thomasliebenau]

Hi @jimkring,

I deleted the comment as I found some bad VI's in the folder to build a package from.
After solving this the beta is still not able to build a package that uses FPGA and FlexRio add-ons

Thomas

[jimkring]

@thomasliebenau OK, thanks for that extra info. This gets a little bit trickier for FPGA VIs, due to how LabVIEW loads execution targets into memory and resolves symbolic paths with LVAddons. We'll have another test build you can try, soon.

[jimkring]

@thomasliebenau would you please try this new build: vipm-24.1.2686-f2beta-windows-setup.exe.zip

Note: This should no longer show the missing FPGA items dialog, but it's not certain whether the full build will succeed -- that hasn't been tested yet with LabVIEW FPGA. We'll keep our fingers crossed...

[thomasliebenau]

Hi @jimkring,

I tested your new build right now. sorry to say it still aborts building because of missing files

[thomasliebenau]

If I try to build without compiling source files right ahead in a 2nd run vipm dies

[jimkring]

Hi @thomasliebenau. Thanks for that info.

There's a test I'd like you to try, if you're willing.

Back up this file -- we're going to modify it and you'll want to restore the original.

C:\Program Files\JKI\VI Package Manager\support\callbacks.llb\Check if File or Folder Exists [Multiple].vi

Modify it's block diagram to force an output of TRUE for every file.

Then, try to build and see what happens. It'll either work or you'll get a new type of error.

[jimkring]

@thomasliebenau could you also create (and share with us) a very small VI Package project (maybe a single VI in your package) that calls FlexRIO and produces errors during the build? This will help us reproduce the issue on our end. If that works, you could zip this small project folder up and attach it here. Or, you could create a small test repo in GitHub that you can point us to.

[thomasliebenau]

Hi @jimkring,

I have to postpone my support here a little as I have to move on to a different task.

One more thing I noticed: Here are 2 people with 2 different environments working:
(1) my college has a full FPGA development environment. His project doesn't show any issues, but he can't build my package because of different folder structure and pre/post actions in our vipb
(2) me having only host side of FPGA installed. I can now see again some missing files in lvproj which are never called in any host vi. This we have to sort out as we work on in this task very soon.

When I come back to this task I will try to build the package at my colleges environment and also try to provide a simplified package to you.

best regards
Thoma