Kristoffer Carlsson
Kristoffer Carlsson
It seems so since there is an issue open about it here https://github.com/JuliaLang/julia/issues/51751. ;)
You would pretty much have to do the same as Julia itself gets built and distributed: - Build Julia on those platforms that you want to support - Host the...
> Do I get this error because of a new packagecompiler.jl version or Julia version? You could try go back to either an earlier PackageCompiler or julia version and see...
PackageCompiler is not very smart when you use a local build that includes a bunch of extra stuff that is not present in a release build that your download. But...
Could be related to https://github.com/JuliaLang/PackageCompiler.jl/issues/786, ref https://github.com/JuliaLang/PackageCompiler.jl/pull/750
> I've been trying to follow the "toy application" tutorial, Which one?
You should probably try https://julialang.github.io/PackageCompiler.jl/stable/apps.html. That is some old document that has been removed from the manual (which is hosted at https://julialang.github.io/PackageCompiler.jl/stable/index.html).
Would it be possible to setup a repository with code that reproduces the issue? It is hard to do much with the information given in here.
> A build flag to turn off this import behavior would probably be good enough as I'm not sure what the import to Main is dedicated for It is there...
There are two different issues being discussed here: 1. The OP which is caused by us trying to make packages available in Main. If two packages have the same name...