Closed markghayden closed 8 years ago
Yes. That's working exactly as intended. There can only be one cross-compiler per opam switch; use something like opam switch 4.02.3+android-arm32 --alias-of 4.02.3+32bit
, opam switch 4.02.3+android-x86_32 --alias-of 4.02.3+32bit
, etc to create a switch per deployment target, and then install the packages you need in every switch independently (the switches are not linked in any way).
I know, annoying. There is nothing I can do about it and still be able to maintain the cross-switches in a sane way. It's an opam deficiency. I've suggested a fix but no one has implemented it yet.
Thanks for the explanation and work-around —M
On Apr 26, 2016, at 7:44 PM, whitequark notifications@github.com wrote:
Yes. That's working exactly as intended. There can only be one cross-compiler per opam switch; use something like opam switch 4.02.3+android-arm32 --alias-of 4.02.3+32bit, opam switch 4.02.3+android-x86_32 --alias-of 4.02.3+32bit, etc to create a switch per deployment target, and then install the packages you need in every switch independently (the switches are not linked in any way).
I know, annoying. There is nothing I can do about it and still be able to maintain the cross-switches in a sane way. It's an opam deficiency. I've suggested a fix but no one has implemented it yet.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/whitequark/opam-cross-android/issues/18#issuecomment-214954042
We haven't tried to build x86 android cross compilers yet, but it seems the directory tree would be an issue. For example, it seems the armv7 and x86 toolchains would both install in the same android-sysroot directory:
.opam/4.02.3+32bit/android-sysroot