Split off headers into libcxx-devel
#190
Conversation
h-vetinari
requested review from
SylvainCorlay,
beckermr,
inducer,
isuruf,
jakirkham and
timsnyder
as code owners
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
| - {{ pin_subpackage("libcxx", exact=True) }} | ||
| - {{ pin_subpackage("libcxx", max_pin=None) }} |
There was a problem hiding this comment.
OK, I think I get now how this solves conda-forge/clangdev-feedstock#310.
If we're using the libcxx-devel 16.x headers to compile something, while having libcxx 20 in the environment, that does run the risk of running into minor ABI differences (and potentially missing symbols, if some got removed in later libcxx), but that's still essentially the same standpoint as we have already, i.e. "libcxx is essentially ABI-stable (and the enormous effort to properly handle any differences isn't worth it, given the relative rarity of breaks)"
|
Failing tests against clang 15 were fixed by conda-forge/libcxx-testing-feedstock#12. This should be ready IMO. |
this does not seem necessary to build, and prevents us from letting `clangxx` depend on `libcxx-devel` (because it would create a build cycle); see conda-forge/clangdev-feedstock#315 (comment)
Redo #183 after #187 and conda-forge/clangdev-feedstock#311 prepared the way.