You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I created a custom device, but then wanted to move the project to a location that I use for development. After moving (and before building in the original location), I cannot successfully run a Configuration Release build. I get an error dialog with the message:
Error 7 occurred at Copy in LLB Pre-Build CHM Build.vi …
LabVIEW: File not found. \Help<cd_name>.chm
The generated Custom Device project Help path seems to be hard-coded at generation time in file \Help\Build.cfg. The path is stored in element name Base Path.
To Reproduce
Steps to reproduce the behavior:
Run the wizard using Create Project... within LabVIEW (NI Veristand, Consolidated NI Veristand Custom Device).
Name the custom device and Finish.
Explore to the location and move the entire cd project folder out of its location to another location on disk. do not just copy the project as this will leave duplicates in place and will mask this bug.
From its new location, open the LV project and run a Configuration Release build. You should see the error dialog quickly and the build will fail.
Expected behavior
You should be able to move these custom device projects around and run successful builds without having to modify a file each time.
Screenshots
Desktop (please complete the following information):
OS: Windows 10
Version: LV 2017 (but can be any version supported by the new Wizard
The text was updated successfully, but these errors were encountered:
Describe the bug
I created a custom device, but then wanted to move the project to a location that I use for development. After moving (and before building in the original location), I cannot successfully run a Configuration Release build. I get an error dialog with the message:
Error 7 occurred at Copy in LLB Pre-Build CHM Build.vi …
LabVIEW: File not found. \Help<cd_name>.chm
The generated Custom Device project Help path seems to be hard-coded at generation time in file \Help\Build.cfg. The path is stored in element name Base Path.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You should be able to move these custom device projects around and run successful builds without having to modify a file each time.
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: