The current mechanism for substituting the LabVIEW version used to build a given repo only substitutes the year version. This was fine when we only built for 32-bit LabVIEW, but with the addition of 64-bit support, we need to be able to build nipkg files that install to the correct location based on architecture. This is required in order to build packages for the custom device build tools and LabVIEW scripting APIs and examples.
buckd
commented
3 years ago
The current mechanism for substituting the LabVIEW version used to build a given repo only substitutes the year version. This was fine when we only built for 32-bit LabVIEW, but with the addition of 64-bit support, we need to be able to build
nipkgfiles that install to the correct location based on architecture. This is required in order to build packages for the custom device build tools and LabVIEW scripting APIs and examples.