There are the variables CONAN_BASE_PROFILE and CONAN_BASE_PROFILE_BUILD that allow to set two profiles, but this is error-prone when we just want to continue to use the automatic generated profiles since CPT / Conan seems to look into a different path for the profiles specified in those variables.
i.e. defining CONAN_BASE_PROFILE_BUILD=default does NOT allow to use the generated profile as build and host profile which is the goal. (e.g. /home/conan/.conan/profiles/default (generated) vs /home/runner/.conan/profiles/default (GitHub Actions inside a Docker container))
Croydon
commented
2 months ago
Right now CPT uses only one profile by default.
There are the variables
CONAN_BASE_PROFILEandCONAN_BASE_PROFILE_BUILDthat allow to set two profiles, but this is error-prone when we just want to continue to use the automatic generated profiles since CPT / Conan seems to look into a different path for the profiles specified in those variables.i.e. defining
CONAN_BASE_PROFILE_BUILD=defaultdoes NOT allow to use the generated profile as build and host profile which is the goal. (e.g./home/conan/.conan/profiles/default(generated) vs/home/runner/.conan/profiles/default(GitHub Actions inside a Docker container))