[minor] Add Custom Post-Install Action VI to Fix Mangled Path to '.gplugindata' File #36
Conversation
This file contains 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
…mangled path of gplugindata file
labview/build specs/Install Custom Actions/Post-Install Custom Action.vi
Show resolved
Hide resolved
Prem-MysteryPro
approved these changes
Mar 13, 2025
varshini-senthil
requested review from
dixonjoel,
csjall and
jasonmreding
as code owners
jasonmreding
approved these changes
Mar 14, 2025
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.
What does this Pull Request accomplish?
This Pull Request adds a new
Post-Install Custom Action.vito theInstrumentStudio Plug-In Generator.vipbbuild specification. This post-install custom action fixes the path of theInstrumentStudio Plug-In Template.gplugindatafile in the plugin library template, which is mangled by VIPB during package installation.Context
VIPB appears to have a bug that mangles the path of the
.gplugindatafile in the plugin library template during package installation.Path to the '.gplugindata' file as mentioned in the template library file present in source:
Path to the '.gplugindata' file as mentioned in the template library file present in the deployed location:
Note
The mangled path interestingly does not affect the plugin generation process in the Generator tool.
Why should this Pull Request be merged?
This Pull Request should be merged to fix the mangled path to the
InstrumentStudio Plug-In Template.gplugindatafile in the plugin library template during package installation, and to ensure proper linkage between deployed files and their libraries.What testing has been done?
Built package, installed and verified proper linkage between deployed files and the libraries.