Conversation
|
this is failing on macOS, which I lightly started debugging, not sure what the issue is, but there's clearly a mismatch in toolchain selection or something so the cmake invocation is getting macOS args |
|
related bazel-contrib/rules_foreign_cc#289, but I don't know why this works fine with the bazel core NDK infra and not this repo |
I'll see if anyone might have an idea of what's going on |
|
thanks that's where I'm surprised that something changed here, but I haven't dug super deep. I imagine someone more familiar with these toolchain setups would know the issue off the top of their head |
|
@ahumesky you hear any useful tips? |
|
Let me follow up on some threads. |
|
cmake default https://github.com/Kitware/CMake/blob/239beca1e3743ec693643869621cd0e41ed10a16/Modules/Platform/Darwin.cmake#L60 added since it's picking the wrong platform for sure |
|
and you're not able to repro this locally i assume right? |
|
oh i think it repros locally too yea. it's definitely a difference in the toolchain configuration somewhere |
|
ah ok that's good -- much harder if it just repros on CI |
|
I think the problem basically comes down to this: rules_foreign_cc / cmake / |
|
it's not just about that flag though, you can see it's adding many macOS specific flags like |
|
oh i didn't realize there were more problematic values in there. the cmake() rule is grabbing the cpp toolchain: and I believe this is all going through the legacy toolchain resolution (especially with |
|
hmm, although, there's a split transition on android_binary which should have translated |
1ddc420 to
890ee63
Compare
|
yea avoiding with |
|
Ok actually I think this is just a rules_foreign_cc issue that wasn't a huge deal before but was uncovered because of switching to lld in the NDK. Tracking here bazel-contrib/rules_foreign_cc#289 |
890ee63 to
8cde187
Compare
|
@ahumesky can you review this one? |
No description provided.