LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Labwindow 2017 batch build compiling extra files depending on which project is active.

I have a workspace with 6 projects.  3 projects include the instrument function panel HP66000.FP.  3 projects are very simple that only have *.c, *h and *.UIR files.  Problem: when I have one of the projects active that includes the HP66000.FP, the Batch Build --> Rebuild feature adds and compiles HP66000.c in every project.  If I have one of the projects active that does not include the HP66000.FP, the Batch Build --> Rebuild feature does not add the HP6600.c to the projects without the HP66000.FP.

 

This issue may be similar to the one documented in https://forums.ni.com/t5/LabWindows-CVI/CVI2013-Batch-Build/td-p/3136452.

 

There are several simple methods to work around this issue.  However, I cannot figure out how to fix this.  What can I do?

 

To duplicate: create 2 simple Hello World projects in 1 workspace.  Batch Build both (Release) and they compile as expected.  Then add HP66000.FP (or maybe any function panel?) to one of the projects.  Set that project active and Batch Build again.  Both projects compile the file HP66000.c (with errors in this case), but we don't want HP66000.c included in the other project.  [I believe we down loaded the HP66000 driver from NI or maybe Keysight.]

 

LabWindows/CVI 2017 17.0.0 (295)

Windows 10

HP66000 driver version: B.00.00  05/01/00  Rebranded for Agilent Technologies.

 

 

0 Kudos
Message 1 of 1
(2,020 Views)