NI Package Builder - Allow absolute paths for build locations

[jyoung8711]

It would be nice to define "absolute paths" for packages, installer, and feed builds.

I applaud the relative path detection used (better than that used in LabVIEW builder!), but sometimes, I just need to define an absolute (In my case that path is actually defined directly off of a root drive (E:\Builds\...), so that all of my build artifacts are in a well defined location...

[Scott_Richardson]

You are correct that NIPB changes absolute paths to relative when they are above and parallel to the solution. This occurs when the property is set. The path is obviously maintained when from a different root that the solution. I am not aware of any workaround at this time.

[jyoung8711]

Scott-- That indeed matches my experience... While this is nice for many use cases, our company typically builds to a set of known locations which are the same across development systems, but the "development spaces" are different depending on user preferences... So while the path I posted maps to E:\Builds\... for me, it will map to a completely non-sensical location for other users.

Having the option to to make it an explicit path (maybe through a right click option?) would be very beneficial.

Thanks.

[Scott_Richardson]

Thanks for the follow-up. One option for NIPB to consider is only convert to relative if selected via the Browse button and not when editing the path in the property text field. 

[jyoung8711]

Scott -- Yes, for what it's worth, that was actually my exact expectations when I was working with the software 🙂 

(ie that when edited directly, it would take that path explicitly (regardless of whether it's relative/absolute), and when it's edited through the file browser, it would preferentially choose a relative path)

[smi38]

Yes it should be possible, exactly like the LabVIEW installer module allows it :

[Scott_Richardson]

NI has released Package Manager 2023 Q3 and added custom directories support, such as D:\my directory\, to the File Agent's instructions file, so when building packages using nipkg.exe the package can install files on any drive or network path. 

Note that "package builder" applications, like LabVIEW and NI Package Builder, will need to expose this capability before it is available in those applications.