James

> May I ask what version of GCC you're using in your non-cross-compile testing? Our local build machines are using GCC 4 whereas our cross-compilation buildroot-generated toolchains are GCC 8....

> I'm at a fork in the road: litter conanfile.py and CMakeLists.txt files with what should be implicit transitive shared library dependencies or enable the experimental feature. The incubating page...

Thanks for the feedback. Yes, it seems that this might be the way you can move forward now. The problem is that unfortunately, it is not possible to accelerate the...

Thanks for the feedback. Still, it seems the right solution is to use the new ``CMakeConfigDeps`` generator, and report if it is working or not, to get it out of...

> @memsharded thanks for the investigation. Just to clarify, the motivating case I described in https://github.com/conan-io/conan/issues/18803 is a plain and simple conan create --build=compatible. If the remote has no compatible...

Hi @gpxricky Thanks for your question. I am not very sure what you mean. If you use Conan for dependencies, then whatever you do with your CMake project you can...

Hi @gpxricky Any clarification for the above comment? Thanks.

> sorry for late feedback. At the end the question is whether using features like conan build is really useful in such a scenario or if it makes more sense...

Hi @Todiq The ``CC_FOR_BUILD`` variable is set for cross-builds: ```python if self._is_cross_building and self._conanfile.conf_build: compilers_build_mapping = ( self._conanfile.conf_build.get("tools.build:compiler_executables", default={}, check_type=dict) ) if "c" in compilers_build_mapping: env.define("CC_FOR_BUILD", compilers_build_mapping["c"]) ``` But that...

> So it seems it is more a recipe or library issue that somehow hardcodes the usage of gcc somewhere? Yes, unless proven otherwise, it doesn't look like a client...