LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW OOP name collision during build

Solved!
Go to solution

Hi everyone,

 

we are testing OOP in LabVIEW. I made a camera class and get this warning during build:

 

"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:\CTT\CTS\Hardware\Camera\IMAQ-Cam\checkimagerdy.vi
C:\CTT\CTS\Hardware\Camera\checkimagerdy.vi
C:\CTT\CTS\Hardware\Camera\configure.vi
C:\CTT\CTS\Hardware\Camera\IMAQ-Cam\configure.vi

..lots more....

"

 

'Use LV 8.x file layout' is not checked.

The VIs seem to work in the exe.

 

LV Class.jpg

 

Any ideas?

Thx in advance

 

0 Kudos
Message 1 of 7
(4,125 Views)

Hello Tesla1977,

looks like you used the same VI names for both classes, the Camera.lvcall and the IMAQ-Cam.lvclass. That´s why you get the warning of duplicate file names.

 

project explorer.jpg

 

Best regards

0 Kudos
Message 2 of 7
(4,056 Views)

Camera is the parent class, IMAQ-Cam the child class, so yes, VI names are the same.

 

0 Kudos
Message 3 of 7
(4,049 Views)

May I ask what LabVIEW version you are using?

0 Kudos
Message 4 of 7
(4,027 Views)

It's 2015.

0 Kudos
Message 5 of 7
(4,015 Views)
Solution
Accepted by topic author Tesla1977

How are these classes organized on disk and how are you configuring the destination directory of these classes and methods for that build? I wouldn't think either of those should matter but if it is something to do with the configuration we might be able to get a pretty simple case that throws these warnings.

 

Edit: I'm guessing this isn't a problem if you want to statically call any of these methods but could mess up dynamic calls if methods are being renamed, is that the concern?

Matt J | National Instruments | CLA
Message 6 of 7
(4,000 Views)

Thanks for your help.

 

Looking at the build configuration solved the problem.

At "Source Files" my new virtual folder with the classes was not in "always included". I changed that and now the build finishes without any warnings.

 

 (how do I delete attachments while editing a reply?)

0 Kudos
Message 7 of 7
(3,991 Views)