@JanDorniak99 has commented about using Yocto cmake toolchain file instead of environment variables as we are doing now. Since Yocto 4.0 (2022) it's able to generate CMake toolchain files, which worth a try, since Conan client now supports natively those toolchain files too and it's much safer than env vars.
So, I'm not a Conan user, but decided to drop in here because I found a Yocto-related issue on your GitHub in an unrelated search. This didn't feel like something to open an issue on your GH, but just as an FYI, since Kirkstone (4.0), when building an SDK, Yocto generates CMake toolchain files to use after installation. One that doesn't need any sort of environmental variables set to work. I've also found Yocto maintainers generally receptive, so if you can't get everything working on your end, maybe try working with them? Most of the code actually driving Yocto builds is Python (with some shell in places), so it's not an unfamiliar language for you folks here. In case anyone is interested, here is the issue for generating that toolchain file https://bugzilla.yoctoproject.org/show_bug.cgi?id=14644
@JanDorniak99 has commented about using Yocto cmake toolchain file instead of environment variables as we are doing now. Since Yocto 4.0 (2022) it's able to generate CMake toolchain files, which worth a try, since Conan client now supports natively those toolchain files too and it's much safer than env vars.