Provisions for installing library versions for multiple platforms about binarybuilder.jl HOT 2 CLOSED

A very interesting proposition. The way I have BinDeps2 structured right now, binaries for different platforms have their target platform encoded in the filename (e.g. libfoo.x86_64-linux-gnu.tar.gz). Binaries are installed to a Prefix, and I would argue that there's no point in mixing binaries of different architectures together into the same prefix, so for a usecase like this, I would suggest the best practice would be to create Prefix for every architecture you're interested in, and install the binaries you want into the relevant prefix. Because cross-compiling is something that's impossible now, and likely to be rare at best, I think keeping the basic installation elements flexible (as they are now) combined with a bit of custom tooling around BinDeps2 is the appropriate level of support for this.

from binarybuilder.jl.

This is possible now; by using the mid-level Artifacts plumbing, you can do things like pass ensure_artifact_installed() an explicit platform object to get the appropriate artifacts put on-disk. Forcing a JLL package to think it is a different package will be considerably harder, but that is of questionable utility.

from binarybuilder.jl.