-
Notifications
You must be signed in to change notification settings - Fork 945
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clang with MSVC-like cross build for windows bin from ubuntu have configuration confusion #9505
Comments
When I use conan under windows with clang-cl, my profiles look like this. |
@dmn-star Profile 1:
Error outPut1:
Profile 2:
error output 2:
|
Profile 1
|
This PR #11492, merged for next 1.53 contains a few changes to better support clang in Windows, mainly for the new There are some other pending issues about the Windows subsystems environment management, we are also trying to improve them in #12178, so if you are using Clang in some subsystem and depend on the environment, you might want to track this PR too. Closing this issue now, but we know that there might still be some gaps, so please try to update to the new integration (this is necessary for 2.0 anyway), and report what might still be failing against this new integration. The best starting point would be the tests in https://github.com/conan-io/conan/blob/develop/conans/test/functional/toolchains/cmake/test_cmake_toolchain_win_clang.py, or using any of the predefined templates |
Use the following dockerfile to build a cross-compiled windows program image, based on clang + wine + msvc tools:
DockerFile View
The matching cmake toolchain file
ToolChain Files View
When I set the profile host as follows:
The following error will appear:
When I set the profile host compiler to clang, it is as follows:
The following error will appear:
There is no libzlibstatic.a in the directory, but has zlibstatic.lib 。 I think it is correct build(), but there are some errors in package(), right? Didn't deal with the situation of clang cross compile windows bin ?
The text was updated successfully, but these errors were encountered: