I’m trying to deploy a DLL compiled with latest PackageCompiler.jl on Julia1.0 to a different computer. I’ve found a severe problem with loading of DLLs of used packages. The trouble-making DLL’s are:
- libopenspecfun.dll from SpecialFunctions,
- libRmath-julia.dll from Rmath
- libddierckx.dll from Dierckx
All of them use hardcoded (from static compillation point of view) dll location using a common construct, e.g.
const libddierckx = joinpath(dirname(@__FILE__), "usr\\bin\\libddierckx.dll")
Could you please point me to a workaround or explanation how one could mitigate these hard-coded paths so that the libs (DLLs) load from one directory (the same where libjulia.dll etc. live)?
The problem is, also whenever I run
pkg"gc" then there is high chance a newer version of the package exists and the old is deleted, making the static compiled work unusable. I’m happy to send an PR but I don’t know where to start or if this is a known bug, backlog issue or strategic core-dev decision.