Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
mdcerna opened this issue Jun 12, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@mdcerna
Copy link

mdcerna commented Jun 12, 2019

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:

  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):

  • OS: Windows 10
  • Version: LV 2017 (but can be any version supported by the new Wizard
@mdcerna mdcerna added the bug Something isn't working label Jun 12, 2019
@rtzoeller
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants