build Error copying files. Librarian Path Location.vi

[petitprince]

Hi,

I would like to build my labview application that depend of 2 sdk and related dlls. When I try to build I obtain the error :
Error copying files.
Source: ..\Program Files\Carl Zeiss\Micro ToolBox\DLL_32\lamp.dll
Destination: D:\MJ-ZAL beta 2\builds\data\lamp.dll

Librarian Path Location.vi

I checked that the file reported is accessible. I also try to add in in the project explorer, in this location, and moving it in the program dir, but it's always the same!

thanks for your help

[Mark.K]

Greetings,

I was unable to reproduce your error by implementing an SDK LabVIEW 8.0 EXE from this example on the web:
Swap Mouse Buttons in LabVIEW

I've attached the related code, project, and built EXE in a zip file.  It seems to work fine, but the main thing is that your DLL's getting called must be in the data directory next to your EXE.

This link might help as well:
Calling the Win32 SDK

You may want to try testing your SDK DLL calls in the simplest way possible in a separate VI, project, and build spec.  This may help isolate the build problems you're having with your overall application.  Best of luck!

[petitprince]

Hi,

I'm sorry for the very long delay for replying. Actually I tried to build on 2 different Pc and I have the same error (Labview 8 /spring 2006). With your example, I end up with

Error 7 occurred at Invoke Node in ABAPI Dist Build App from LLB.vi->ABAPI Build Application.vi->EBEP_Invoke_Build_Engine.vi->EBUIP_Build_Invoke.vi->EBUIP_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux.
---
NI-488:  Non-existent board.

Method Name: Build:Application



So if anyone has an idea of the issue.

Thanks

[Kalin_T]

Hi petitprince,

In LabVIEW 8.0, the Application Builder was modified to look for the Help file paths for any VIs within the executable or the Help file paths for the executable itself. This error occurs when one or more of these help file paths is invalid. Some LabVIEW VIs currently have broken help files, but these are being identified and fixed for the 8.0.1 patch. If the problem VI is an Express VI, replacing the Express VI with explicit code may get rid of the error.

Another source of the problem could be the Help files for the top-level VI. To check this, go to File»VI Properties»Documentation and verify the Help tag and Help path. Once the broken Help file path is corrected, the build should continue without the above error.

Hope that helps!