You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use msys2 as my shell (git-sdk-64), on my M:
I set up a python devenv with a dos prompt first, using Windows python (not msys),
Then in msys terminal, I run . /m/conan4/devenv/Scripts/activate
This works with most things - let me know if I should be doing things differently.
(I want to build with msvc17 and (in future) clang+msvc)
Now, I have 2 options when running my terminal. I'll just talk about DOS prompts, but I actually use Windows Terminal.
I start a plain DOS prompt. Enter bash. ie standard msys startup.
I run the MSVC command prompt setup first, and THEN enter bash.
The ICU build works with approach #2, which means the recipe DEPENDS ON the environment of the calling conan command. It SHOULD be using the conan environment setup, like all the other recipes!
So, anyway, without the initial MSVC environment setup,
I then run my big conan install for my recipe, and this is what happens when it comes to ICU's build:
see log below
NOTE that it complains, and then asks me to check config.log
I checked, the difference is there are MSVC bin paths in the PATH variable in the working example.
paulharris
changed the title
[package] icu/74.2: won't build with msvc17 from within msys2 shell environment
[package] icu/74.2: won't build with msvc17 from within msys2, without MSVC paths pre-setup
Apr 20, 2024
I guess the base question is:
Must I always run conan builds from within a terminal with MS vcvars already executed?
Or is this something I should expect conan to initialise with each package build step?
Description
I use msys2 as my shell (git-sdk-64), on my M:
I set up a python devenv with a dos prompt first, using Windows python (not msys),
Then in msys terminal, I run
. /m/conan4/devenv/Scripts/activate
This works with most things - let me know if I should be doing things differently.
(I want to build with msvc17 and (in future) clang+msvc)
Now, I have 2 options when running my terminal. I'll just talk about DOS prompts, but I actually use Windows Terminal.
The ICU build works with approach #2, which means the recipe DEPENDS ON the environment of the calling conan command. It SHOULD be using the conan environment setup, like all the other recipes!
So, anyway, without the initial MSVC environment setup,
I then run my big
conan install
for my recipe, and this is what happens when it comes to ICU's build:see log below
NOTE that it complains, and then asks me to check config.log
I checked, the difference is there are MSVC bin paths in the PATH variable in the working example.
Package and Environment Details
Conan profile
======== Input profiles ========
Profile host:
[settings]
arch=x86_64
build_type=Debug
compiler=msvc
compiler.cppstd=20
compiler.runtime=dynamic
compiler.runtime_type=Debug
compiler.version=193
os=Windows
[options]
libcurl/:with_ssl=schannel
mxrap/:shared=True
qt/*:openssl=False
[conf]
tools.cmake.cmaketoolchain:generator=Ninja
Profile build:
[settings]
arch=x86_64
build_type=Release
compiler=msvc
compiler.cppstd=20
compiler.runtime=dynamic
compiler.runtime_type=Release
compiler.version=193
os=Windows
[options]
libcurl/:with_ssl=schannel
qt/:openssl=False
[conf]
tools.cmake.cmaketoolchain:generator=Ninja
Steps to reproduce
Open MSYS
conan create . --version 74.2 --user test --channel test1 -pr:h theprofileh -pr:b theprofileb
Logs
Click to expand log
The text was updated successfully, but these errors were encountered: