Data folder after comiplation

[ThomasThePommes]

Hello,

I have a problem. Might be a simple one but I couldn't find a solution so far.

When I compile my VIs LabView creates a "data" folder with dll's I used. Now I want to use a different (static) folder for my dll's. Is it possible to say my programm that the libarys are located at a different place? 

[PalanivelThiruvenkadam]

Do you mean Data Folder" LabVIEW Data" Which is "C:\Users\xxxxx\Documents\LabVIEW Data"?

[ThomasThePommes]

No I mean the folder that is created when I just build an exe. In this case I get the .exe, an .ini, an .aliases and the data folder with all dll's.

The compiled programm uses the dll's from these data folder. But I want to load the dll's from a different directory. Like c:\LabViewDLL for example.

[ThomasThePommes]

Maybe an update to my problem:

I found out how to change where the directory is created (build specifications -> Destinations). But now I encountered a different problem... maybe my core problem.

I want to use the exact dll's that I used in my VIs. I don't want the application builder to grab all the dll's and put them in a new directory. My idea was to simply use the source directory as the directory for supporting data. But LabView tells me that these two directorys could not be the same.

So the question should be: Is there a way to use the dll's from my source directory (like c:\LabViewDLLs) instead of the "new" dlls that the application builder creates.

[crossrulz · Accepted solution]

---

@ThomasThePommes wrote:

So the question should be: Is there a way to use the dll's from my source directory (like c:\LabViewDLLs) instead of the "new" dlls that the application builder creates.

---

In the executable build spec, go to the Additional Exclusions category.  There is an option there to "Exclude dependent shared libraries".  Make sure that is checked.

[ThomasThePommes]

---

@crossrulz wrote:

---

@ThomasThePommes wrote:

So the question should be: Is there a way to use the dll's from my source directory (like c:\LabViewDLLs) instead of the "new" dlls that the application builder creates.

---

In the executable build spec, go to the Additional Exclusions category.  There is an option there to "Exclude dependent shared libraries".  Make sure that is checked.

---

Oh perfect thats exactly what I was looking for. Thank you.