search

conda-forge / ctng-compiler-activation-feedstock

A conda-smithy repository for ctng-compiler-activation.
BSD 3-Clause "New" or "Revised" License
13 stars 22 forks source link

Add `clang{,xx}` compilers; build for multiple clang versions #101

Closed h-vetinari closed 4 months ago

h-vetinari commented 4 months ago

This is a continuation of #100, with the main change of not building clang alongside, but elevating it to a separate build, in the spirit of Isuru's statement:

I think of this feedstock as Linux compilers

Clang is a full-fledged compiler for linux, so I'd like to treat it like one (by being able to build for several versions). The only overlap between compiler_vendor == "gcc" and "clang" is that binutils_{{ cross_target_platform }} gets built in each job, but will only be uploaded once (due to coinciding hashes). This is already the case before this PR for different GCC versions, so that should be a non-issue IMO.

Rather than building clang 16 x gcc {11, 12, 13} (like in #100), I'd prefer to build clang {16, 17, y} x gcc {base}. The interaction with the GCC version only comes in through the dependence on libgcc-devel_{{ cross_target_platform }}, and I think it's more worthwhile to cover more clang versions, than to enable only old(er) clang, but with all versions of libgcc-devel.

I actually also wanted to tackle https://github.com/conda-forge/clang-compiler-activation-feedstock/issues/118, but realized that we cannot introduce clang / clangxx outputs without renaming them on the clangdev feedstock first.

conda-forge-webservices[bot] commented 4 months ago

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 (recipe) and found it was in an excellent condition.

beckermr commented 4 months ago

I'll defer to @isuruf. This feedstock has moved beyond me.

h-vetinari commented 4 months ago

Obsoleted by #102