LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

File name collision during build that includes Report Generation toolkit. How to correct?

When I switched to LV 8.6 (it's also in 8.6.1) I started getting a file name collision warning when building an installer that included the Report Generation toolkit. The executable works, but I don't like to leave warnings uninvestigated. I don't understand 1) why it's happening now and 2) what it's recommending for the fix. Here's part of the actual warning it gives.

 

LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts.
 
The following files were moved to a unique location:
 
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Control Image to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append Control Image to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append File to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append File to Report.vi
C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\Append Horizontal Line to Report.vi...........

 

0 Kudos
Message 1 of 6
(3,568 Views)

Hi GS,

 

The architecture of the Report Generation Toolkit was changed in LabVIEW 8.6 to utilize LabVIEW Classes.  As such, there are some warnings during an EXE build because the class VIs have identical names.  Classes were not used in the toolkit in LabVIEW 8.5 and previous...that's why you didn't see any warnings during the build until now.

 

Your EXE should still function properly, and you shouldn't have to change anything about your build.  The purpose of the warnings is to let you know that the duplicate-named VIs needed to be handled differently during the build.

 

-D

0 Kudos
Message 2 of 6
(3,553 Views)

We have the same problem. ..

 

An implication of this issue is that the build creates three subdirectories which have to be moved together with the exe in order for the exe to work if deployed to another folder - how do we fix this problem without having to deploy all these dependency vi's?

 

Otherwise this would appear to negate the benefit of building an executable in the first place.

0 Kudos
Message 3 of 6
(3,517 Views)

Unfortunately, the dependencies are necessary with LVOOP, this thread discusses ways of dealing with the new RGT, and disguising them as dlls

 


_____________________________
- Cheers, Ed
Message 4 of 6
(3,506 Views)

Unfortunately, the dependencies are necessary with LVOOP, this thread discusses ways of dealing with the new RGT, and disguising them as dlls

 

Many thanks for that thread link.

0 Kudos
Message 5 of 6
(3,500 Views)

We're looking into ways to address the issue of having separate files for your EXE in a future LabVIEW version.

Message Edited by Darren on 03-03-2009 10:30 AM
0 Kudos
Message 6 of 6
(3,489 Views)