search

ni / niveristand-custom-device-wizard

LabVIEW project template for VeriStand custom devices
MIT License
13 stars 7 forks source link

Cannot move the customproject and successfully run a Configuration Build. #7

Open mdcerna opened 5 years ago

mdcerna commented 5 years ago

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\.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:

  1. Run the wizard using Create Project... within LabVIEW (NI Veristand, Consolidated NI Veristand Custom Device).
  2. Name the custom device and Finish.
  3. 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.
  4. 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 image

Desktop (please complete the following information):

rtzoeller commented 4 years ago

Once https://github.com/ni/niveristand-custom-device-development-tools/pull/17 lands, we should be able to generate a project that uses relative paths.