© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
It sounds like your are upset that we have closed the bug. I am sorry about that.
What is your use case?
We are now at CMake and CMake is able to build with MinGW out of the box.
I am sure there are some tweaks required to get it to work, but from my experience it should not be a maintenance burden at all to keep MinGW support in our CMakeList.txt.
This is just because we have Windows support and GCC support in it, which is maintained anyway.
The maintenance burden comes in if we maintain this with our CI and together with all dependencies. But If this bug here melts down to keep our CMakeList.txt clean, ther is nothing against it IMHO.
What do you think?