Mac Osx Capitan and DYLD_LIBRARY_PATH about atom-julia-client HOT 6 OPEN

So there's a trick I've just tested. It works fine but doesn't seem satisfying regarding the security of the OS. You can Disable System Integrity Protection as explained here

from atom-julia-client.

Hello Varanas,

Yeah, I did write that ... but that was working on Yosemite, not on Capitan, because :

"El Capitan" has a "security" feature that
prevents passing DYLD_LIBRARY_PATH to child processes. Somehow, that
variable is stripped from the environment.

So even if I launch Atom from the terminal, the DYLD_LIBRARY_PATH is stripped from the environment.

I'll try your proposal and get back to you.

Thanks,
Lionel

from atom-julia-client.

You did write that you

effectively get all the env variables when launching atom with the atom command from the terminal.

And that should be the case, since afaict no child processes are spawned except possibly when starting from the shortcut.

So can't you just write write yourself a script that starts a terminal and start atom from that or something?

Also: Have you tried what I suggested in the other issue?

What you could also try as a workaround is setting Libdl.DL_LOAD_PATH because dlopen should use that for looking up libraries first...

from atom-julia-client.

@lionpeloux Did you resolve this issue? I'd like to add the workaround to the docs for Juno, if it works.

from atom-julia-client.

Does it work to set the environment variable in ~/.juliarc.jl?

from atom-julia-client.

I just ran into this myself.

Does it work to set the environment variable in ~/.juliarc.jl?

Just setting ENV["DYLD_LIBRARY_PATH"] alone doesn't (although it does get reflected in the Atom julia console). But the suggestion to append to Libdl.DL_LOAD_PATH works.

from atom-julia-client.