I’m asking here because I don’t find nothing in the documentation on this topic.
On Windows targets (both 32 and 64 bits) how a Xojo program resolve the file path when loading DLL referred by Declare statements?
There is any feature for the program to control where to look for the requested DLL?
I know that for a single DLL I can set the full path of the DLL itself but how, if possible, can be controlled the loading of any nested DLL required by the first one?
If this process can’t be modified/controlled/changed what are the rules used?
You can specify the full path to the library so this is under program control.
A Xojo app find the "private° dll in the "libs° or “appname libs” folder.
So this can confirm that Xojo is doing something well defined about locating a dll on disk.
What exactly is done and which kind of control can be done in the user application it not documented or not kown to me.
Of note, I’m pretty sure that this path, “MyApplication Libs” is baked into the EXE file when the IDE builds it. So, if you rename your EXE, it will not be able to find the DLLs any longer. Is that true in Xojo?
[quote=37944:@claudia orona flores]
The dll can be development in any program languaje?[/quote]
As far as I know as long as its not exporting C++ classes or C++ mangled names things should just work.
Ok, and are you sure that the DLL is in one of the places that Norman described when you ran the app? (you would be surprised how often people forget to copy the file during testing).