Details
- Reviewers
ruiu rnk - Commits
- rZORG128b5552b868: [MinGW] Implement the -v and --version flags for the MinGW driver
rG128b5552b868: [MinGW] Implement the -v and --version flags for the MinGW driver
rG6863dfaa21db: [MinGW] Implement the -v and --version flags for the MinGW driver
rLLD361016: [MinGW] Implement the -v and --version flags for the MinGW driver
rL361016: [MinGW] Implement the -v and --version flags for the MinGW driver
Diff Detail
Event Timeline
MinGW/Driver.cpp | ||
---|---|---|
144 | Do we need "(compatible with GNU linkers)"? This is a hack for compatibility with configure scripts (https://www.sigbus.info/software-compatibility-and-our-own-user-agent-problem). I don't know much about how linkers are detected on Windows for MinGW, but if you don't need it, you can remove it from the version message. |
MinGW/Driver.cpp | ||
---|---|---|
144 | One of the main selling points of MinGW is that it works with the same configure/autotools/libtool based builds as lots of unix libraries. So yes, unfortunately, the same compatibility hack is needed here as well. Do you want me to bring along a bit more of the comment to point this out, to indicate that this is intentional? |
Added more of the original comment about "compatible with GNU linkers" which also applies for MinGW.
Do we need "(compatible with GNU linkers)"? This is a hack for compatibility with configure scripts (https://www.sigbus.info/software-compatibility-and-our-own-user-agent-problem). I don't know much about how linkers are detected on Windows for MinGW, but if you don't need it, you can remove it from the version message.