Thanks for the answer!

Actually it is a total of three libraries:

• the first one is a module that I load with dlopen. For this one I just implemented a solution where it is installed in the Element Resource directory from CMake, and I then fetch it with a path like SB_ELEMENT_PATH + "/Resource/MyLib.dll". This works.

• the second one is a shared library on which the element directly depends. I fear I cannot use QCoreApplication::addLibraryPath because this library will be required before any code from the SAMSON Element can be executed. I will have a look if I can convert it to a static library.

• the third one is the dynamic library for Intel TBB. One could require the user to install Intel TBB himself. Otherwise it is the same problem as for the second library above.

Hi,

The Element I am developing has dependencies to two other DLLs that are also part of my project. When I launch SAMSON, these DLLs are not found unless they are present in the PATH environment variable.

How should I handle this case? Is it possible to install them automatically at some location recognized by SAMSON?

And, for a later step: will it be possible to also upload them when uploading my Element to samson-connect?

Best,
Alain