@GyrosGeier @jordyd this would just be standardizing on a system-toolchain information file format, right? like a JSON file, telling you about quirks if it's present, and if it's not present the autoconf song-and-dance can generate one for you?
pkgconfig does this for libraries, instead of running detection on /usr/lib/.
@bb010g @jordyd the problem with any tool is that it needs to cover the existing use cases as well, or it is a regression. It was a long battle to get pkg-config to work with cross-compilation, and CMake's toolchain files are also a step backwards compared to interrogating the compiler, because now I have to predict what packages may look for, and provide the value by hand.
Maybe the other way round would be better: packages list values they need, and the configure tool checks If they are known
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!