LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Does the application builder handle path to external DLLs correctly?

Solved!
Go to solution

Hello!

Let's say I have a LV lib with VI, based on a DLL that's in the lib folder. When creating an application I would include the DLL, unless the app builder already does that automatically. The path to the DLL would then change, because it would be placed in the installation folder of the application. 

 

So the question is, will the app builder replace the paths in the DLL calls by a relative one automatically when building the app?

0 Kudos
Message 1 of 8
(1,147 Views)
Solution
Accepted by topic author MaSta

That depends on whether you specify the library path on the block diagram or in the call library node. In the former case they are automatically included, in the latter case you have manual work to do. See this KB article. Maybe also this one.

If your libraries depend on other libraries, you will have to include those manually or make sure they are in the PATH of the target system. (e.g. system libraries or driver installers)

Message 2 of 8
(1,135 Views)

Ok, the solution is actually not to worry at all, because if I put the DLL(s) next to the EXE, it will find them.

Thanks for pointing me. 

 

P. S. "That depends on whether you specify the library path on the block diagram or in the call library node" -> as far as I know, you can specify the DLL path only in the call librarby node settings.

0 Kudos
Message 3 of 8
(1,116 Views)

By default, yes. But there is also this option:

cordm_0-1678382356256.png

 

0 Kudos
Message 4 of 8
(1,104 Views)

Oh! Didn't notice that one. 

0 Kudos
Message 5 of 8
(1,062 Views)

@cordm wrote:

That depends on whether you specify the library path on the block diagram or in the call library node. In the former case they are automatically included, in the latter case you have manual work to do. See this KB article. Maybe also this one.


I think you somehow mixed that up. You first mention the block diagram path and then the Call Library Node configuration. Then you go on to talk about the "former". Maybe in English "former" in such a context means the last option, I interpret it to mean the first option. If my interpretation is used, your statement seems wrong.

Rolf Kalbermatter
My Blog
0 Kudos
Message 6 of 8
(1,054 Views)

Duplicate post after Editing the original post.

Rolf Kalbermatter
My Blog
0 Kudos
Message 7 of 8
(1,052 Views)

You are right, it is the other way around.

So configured in CLN: automatically included, path on block diagram: must include manually.

0 Kudos
Message 8 of 8
(1,042 Views)