01-03-2017 02:37 AM
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.
Any ideas?
Thx in advance
Solved! Go to Solution.
01-04-2017 02:15 AM - edited 01-04-2017 02:15 AM
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.
Best regards
01-04-2017 03:05 AM
Camera is the parent class, IMAQ-Cam the child class, so yes, VI names are the same.
01-05-2017 10:12 AM
May I ask what LabVIEW version you are using?
01-06-2017 01:25 AM
It's 2015.
01-06-2017 07:33 AM - edited 01-06-2017 07:36 AM
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?
01-06-2017 07:46 AM - edited 01-06-2017 07:48 AM
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?)