Action to Build PPLs in Windows and Linux#37
Merged
watsnav merged 53 commits intoni:actionsfrom Mar 18, 2026
Merged
Conversation
Build PPL in Linux and Windows docker container
…/build-lvlibp-win32
Build PPL for win32 in Github runners
be0d1d4 to
4ffb58f
Compare
I was told by Greg Richardson the LabVIEW docker images had 32-bit and 64-bit LabVIEW installed. You just had to point to C:\Program Files... or C:\Program Files (x86)... |
watsnav
reviewed
Mar 17, 2026
scripts/build-lvlibp-github-hosted-windows/BuildLvlibpGithubHostedWindows.ps1
Show resolved
Hide resolved
watsnav
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
For all 3 workflows, the version is of the format
Major.Minor.Build.Patch. If the version string is not available (because of any one of these 4 fields being unavailable), the version will not be updated in the build spec.If a particular build specification is not specified, it builds all build specifications in the project. If a version is provided, it will be applied to all build specifications.
To set the version, the following VIs are used:
Gets the Build specification name, Project path, Target name and Version as input and then calls SetBuildVersion.vi to actually set the version in the build specs based on the version string which is split into a string array.
If no build specification name is given, it iterates through all build specs and calls SetBuildVersion.vi to set the version for all.
Sets the version based on the array of strings. It uses
Set Build Specification Version.vifrom vi.lib folder to do so. This also needs the Build specification name, Project path and Target name. The Target Name defaults to "My Computer".Requirement(s)
Testing