Conda-forge.github.io: [DOC] Compiler flags and where they come from

[jakirkham]

It would be good to document where compiler flags are set in our infrastructure. We may also want to improve visibility about compiler changes so users are aware. This came up recently on Gitter.

cc @conda-forge/core

[phil-blain]

I think another good thing to document would be which feedstock is responsible for which compilers on which platform. This is not at all easy to find for newcomers!

ex. even if you know that Clang is used on macOS, searching for "clang" in the conda-forge org returns 7 results, and it's not clear that https://github.com/conda-forge/clang-compiler-activation-feedstock is the right one.

This info should also be in the README of the respective feedstock, in my opinion.

[isuruf]

I'm the maintainer for all of those, and I simply don't have the time. PRs welcome though.

[jakirkham]

Probably what we need here is a list of places to look for further info. This is my understanding of what that list would look like (please correct me if I'm wrong and fill out any details):

• Linux; GCC - https://github.com/conda-forge/ctng-compiler-activation-feedstock
• macOS, Linux; Clang - https://github.com/conda-forge/clang-compiler-activation-feedstock
• Win, Clang - https://github.com/conda-forge/clang-win-activation-feedstock
• Win, VC - ?
• ?

[isuruf]

https://github.com/conda-forge/conda-forge.github.io/wiki/Compilers

[jakirkham]

That's great Isuru! 😄 So maybe we just need to copy that to the docs somewhere?

[isuruf]

As I said earlier, PRs welcome.

[jakirkham]

@phil-blain, is this something you would be interested in doing? Seems pretty straightforward 🙂

[phil-blain]

@jakirkham I might try to find some time after my current project (https://github.com/conda-forge/gdb-feedstock/pull/23)

[jakirkham]

Sounds good. Getting gdb working on macOS would be nice 😄