[A note of caution to Mac and Linux users]

PS:

This means that any new package built with Windows cannot be installed on any non-Windows systems, effectively eliminating VIPM support for Mac and Linux.

 

If you use VIPM on Mac or Linux, you may want to hold off on upgrading to LabVIEW 2017 until this gets resolved.

Not entirely true. VIPM 2014-linux is able to install for me a lot of packages built with earlier versions of VIPM, on LV-linux 2015, 16 and 17.

[A note of caution to Mac and Linux users]

 

Packages built with VIPM 2017

Yes but - having the sources and the package build specification, known to work VIPM 2017, as well as several LV versions installed, can a package be built with 2014-linux?

 

Specifically I'm thinking at this package. I don't think it contains any code which needs the very latest LV features, in fact it is provided for LV2015. If I try to load its .vipb in VIPM 2014-linux, I just get "VI Package Builder was unable to open the build spec due to an error". Perhaps something offending in this .vipm which could be patched at hand?

 

ref: https://lavag.org/topic/20262-cr-lv-muparser/?do=findComment&comment=123699