Closed vchuravy closed 4 years ago
I downloaded v0.8.1 for Linux from the release page.
ah right! I was normally using it via system image, so it wasn't an issue for that. It will spawn a subprocess to install things in the global environment. I guess I should do this by calling Pkg's API instead.
I realize in the context of installing Julia packages (rather than binaries), we have to make sure there is a Julia compiler binary available and resolve the versions based on that compiler version since Julia packages are not standalone.
This is not a problem when IonCLI is installed normally via Pkg.add
since we can just assume users are using the exact same julia compiler and use that compiler version (via Base.julia_exename()
).
But this can be an issue for the Ion application, which is standalone itself. I guess there is no reliable way to detect the compiler user uses, so I'm thinking about doing it in this way:
JULIA_EXECUTABLE_PATH
, so if users are using a custom executable, ion can use that instead.julia
exists, use this if it existsI think in the future when Ion supports #19 we can just maintain a list of Julia compilers by Ion itself to know which is which and ask for a Julia installation if it cannot find any.
@vchuravy should be fixed in 0.8.4, but if you don't have a julia
command in your shell environment or (it's not the compiler you want to use) you will need to set JULIA_EXECUTABLE_PATH
yourself.