[android] Don't generate a libstdcxx.modulemap

[finagolfin]

Android uses libc++, which already has its own module map.

@egorzhdan, as we discussed, removing this, as I noticed it breaks some tests on the Android CI too.

@compnerd, letting you know in case you have any input.

[compnerd]

Seems reasonable to get the CI back to green, but please do open an issue and tag it - we really should try to get C++ interop working on Android as well.

[finagolfin]

please do open an issue and tag it

Will open an issue, but could you explain what I should do to "tag it?"

we really should try to get C++ interop working on Android as well.

It mostly works, with the Android CI only broken because some new Interop tests were added late last year that happen to interact badly with how Android organizes its C headers. Also, my pull #40779 that moved some Swift memory tags broke one test on the CI. Once this is in, I'll look at those remaining failing tests.

[compnerd]

please do open an issue and tag it

Will open an issue, but could you explain what I should do to "tag it?"

Oh, just reference the issue in the commit message ideally (e.g. this should be enabled and #... tracks it type of thing) or just reference the PR from the issue.

we really should try to get C++ interop working on Android as well.

It mostly works, with the Android CI only broken because some new Interop tests were added late last year that happen to interact badly with how Android organizes its C headers. Also, my pull #40779 that moved some Swift memory tags broke one test on the CI. Once this is in, I'll look at those remaining failing tests.

Thank you!

[egorzhdan]

Thanks!

[finagolfin]

@egorzhdan, if you would just run the CI, we can get this in.

[egorzhdan]

@swift-ci please smoke test

[finagolfin]

Thanks for the quick turnaround.