Setting LD_LIBRARY_PATH to single file exe extraction folder

[ThadHouse]

I have some native libraries for my project, which depend on each other. When using a single file exe, these get extracted properly, however because LD_LIBRARY_PATH isn't set, they don't load correctly. Setting the extract base dir doesn't work, since there are subfolders that are not fixed names. Is there any way to get the bundle id at runtime to be able to set up the library path correctly?

[vitek-karas]

@swaroop-sridhar

[swaroop-sridhar]

@ThadHouse you can use the Assembly.Location on the app's main assembly -- which will point to the extraction location. Can you construct paths to the native DLLs based on this path?

[ThadHouse]

That wouldn't work correctly. Its not having trouble finding the native library I load via P/Invoke, but instead that library has trouble finding its dependents, since the extracted location is not in the Library Search Path. I guess I could P/Invoke manually into the linux loader and set the library search path before my library loads. Seems a bit convoluted and something that should be supported by default, but it would work.

Dependent libraries are fairly common, so it would be nice to have the extraction location in the search path.

[swaroop-sridhar]

@ThadHouse, I understand the point you're making -- that the dependent libraries would be found in the current directory, but not from the extraction location.

I was trying to answer the specific requirement, about locating the extraction location/bundle-ID:

Is there any way to get the bundle id at runtime to be able to set up the library path correctly?

At runtime, assembly-location will be the extraction location, and the last component of that path is the bundle-id.