Add community support for building with MinGW#9137
Conversation
2e2cb37 to
70f2e4f
Compare
35d3037 to
385ff14
Compare
|
Does the |
yes it does. See: But only after applying this unrelated patch: diff --git a/toolsrc/src/vcpkg/logicexpression.cpp b/toolsrc/src/vcpkg/logicexpression.cpp
index ccb8b00c4..eed27bdf3 100644
--- a/toolsrc/src/vcpkg/logicexpression.cpp
+++ b/toolsrc/src/vcpkg/logicexpression.cpp
@@ -68,11 +68,11 @@ namespace vcpkg
add_error("Invalid logic expression");
}
- if (err)
- {
- err->print_error();
- final_result = false;
- }
+// if (err)
+// {
+// err->print_error();
+// final_result = false;
+// }
}
bool get_result() const { return final_result; } |
|
Could you please make a PR for that unrelated patch. It would be much appreciated. We're supposed to support vs2015. |
|
When trying to use this with nuwen-mingw to build boost-stacktrace (and boost in general) it fails with this in install-x64-mingw-dbg-out.log: Successfully built sdl2 with it and boost is not a huge issue (as nuwen-mingw has it already included). |
|
Some extra info that might help, it fails earlier on if I don't have boost-build:x86-windows installed: |
Not all packages would work with this PR, especially those that require a custom build system like boost. Somebody would have to make sure that |
|
@cristianadam Thanks for the PR! We like the idea and implementation. However, since we don't officially support MinGW, the triplet files will need to go into a separate folder: |
|
Hi. Would it be acceptable to merge the PR without the triplet files? |
385ff14 to
80ecd29
Compare
|
@dan-shaw I removed the triplets from the MR. The x64-mingw triplet is nothing more than: I think if |
The CI is stuck since 16th of December. |
|
I don't think we can, the MacOS CI pipeline is still down. |
The macOS CI pipeline is down since 2nd of December 😮 GitHub Actions is up and running fine on macOS, maybe you guys should switch to GitHub Actions ? 😄 |
|
We might merge this and not wait for the MacOS CIs to be back up (since it is taking a while). Pinging @ras0219 for review |
|
The vcpkg-osx-PR is still broken. I've seen that release 2019.12 was done. |
|
@cristianadam See #9600. |
|
/azp run |
|
What's the difference between |
|
@cristianadam |
Are you going to contribute MinGW triplets later? I think it may be very productive idea when |
80ecd29 to
e77da72
Compare
Tested with MSYS2 MinGW 8.3.0, gcc-mcf.lhmouse MinGW 9.2.1, and StephanTLavavej/mingw-distro!
From your MinGW configured shell you could just use vcpkg to configure packages. An x64-mingw triplet would look like: ``` set(VCPKG_TARGET_ARCHITECTURE x64) set(VCPKG_CRT_LINKAGE dynamic) set(VCPKG_LIBRARY_LINKAGE static) set(VCPKG_ENV_PASSTHROUGH PATH) set(VCPKG_CMAKE_SYSTEM_NAME MinGW) ```
547dbf4 to
ff32f46
Compare
|
Now that Community Triplets have been merged in #7976 can you please add a |
x64 tested with https://github.com/StephanTLavavej/mingw-distro x86, arm64, arm tested with https://github.com/mstorsjo/llvm-mingw
Done. The original triplets that I have had are back in. 🤘 |
|
Thanks for the PR! |
* Add support for building with MinGW Tested with MSYS2 MinGW 8.3.0, gcc-mcf.lhmouse MinGW 9.2.1, and StephanTLavavej/mingw-distro! * Add MinGW toolchain From your MinGW configured shell you could just use vcpkg to configure packages. An x64-mingw triplet would look like: ``` set(VCPKG_TARGET_ARCHITECTURE x64) set(VCPKG_CRT_LINKAGE dynamic) set(VCPKG_LIBRARY_LINKAGE static) set(VCPKG_ENV_PASSTHROUGH PATH) set(VCPKG_CMAKE_SYSTEM_NAME MinGW) ``` * Add MinGW community tripplets x64 tested with https://github.com/StephanTLavavej/mingw-distro x86, arm64, arm tested with https://github.com/mstorsjo/llvm-mingw
The merge request adds the following commits:
Tested with the standalone StephanTLavavej/mingw-distro.
The arm and arm64 triplets I tested with the Clang-LLVM/MinGW toolchain.