From: <ml...@di...> - 2014-02-15 19:40:26
|
Gisle Vanem wrote: > It's kind of confusing situation, yes. I cannot advice much on making > mingw.org more acceptable for projects. But the resentment toward > old-school MingW is probably partly because of the somewhat confusing > situation with how both projects define '__MINGW32__'? I'm not seeing an issue with projects having trouble defining #ifdefs between the two versions. Projects have straight out told me they will not support 2 Windows compilers. They will only support the mingw64 project. They refuse to take patches to make mingw (from mingw.org) work. Some of the projects have been downright nasty when I send patches to them to add support for mingw (mingw.org version). It's hard enough porting Open Source projects from other platforms to Windows and getting them to build. Having to worry about whether your using an "accepted" Windows compiler for each particular project makes matters even worse. Would like to hear from others encountering this issue. Please let me know if you have any techniques for working around it. Thanks. I'm building several Open Source libraries and programs from source on several platforms including Windows. So far, when I run into a situation like this, I've written the project off my list of projects to build and looked for a more accomodating cross-platform project. > The situation was frustrating for Mr Lavavej too. So he made his own very > good MingW (x64 native) light-weight distro; > [1] http://nuwen.net/mingw.html > > So when I finally upgrade to Win8.1 (with a i7 CPU?), I will use his > distro to target x64-native. And not the rather confusing distro from > http://mingw-w64.sourceforge.net/. Thanks for the information on this. I'm personally still targeting 32 bit even though I have a 64 bit platform to work with because some of my machines still use 32 bit. However, I know some people who are targeting 64 bit. Sincerely, Laura http://www.distasis.com/cpp |
From: Eli Z. <el...@gn...> - 2014-02-15 20:48:57
|
> Date: Sat, 15 Feb 2014 11:40:18 -0800 (PST) > From: ml...@di... > > I'm not seeing an issue with projects having trouble defining #ifdefs > between the two versions. Projects have straight out told me they will > not support 2 Windows compilers. They will only support the mingw64 > project. They refuse to take patches to make mingw (from mingw.org) work. > Some of the projects have been downright nasty when I send patches to > them to add support for mingw (mingw.org version). > > It's hard enough porting Open Source projects from other platforms to > Windows and getting them to build. Having to worry about whether your > using an "accepted" Windows compiler for each particular project makes > matters even worse. > > Would like to hear from others encountering this issue. Please let me > know if you have any techniques for working around it. Thanks. My technique is very simple: if a project refuses to accept my patches, I then ignore that project's maintainers, and provide my binaries from my site (https://sourceforge.net/projects/ezwinports/). I have never been told that my patches will not be accepted because I use a "wrong" MinGW, but I was told more than once that Windows-related patches are not very welcome. I moved on, and I suggest that you do, too. Life is too short to worry about such upstream maintainers. So I suggest that you decide for yourself which MinGW you prefer, and disregard anyone who tries to affect that decision by this kind of "arguments". |
From: LRN <lr...@gm...> - 2014-02-15 21:03:30
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15.02.2014 23:40, ml...@di... wrote: > Gisle Vanem wrote: >> It's kind of confusing situation, yes. I cannot advice much on >> making mingw.org more acceptable for projects. But the resentment >> toward old-school MingW is probably partly because of the >> somewhat confusing situation with how both projects define >> '__MINGW32__'? > > I'm not seeing an issue with projects having trouble defining > #ifdefs between the two versions. Projects have straight out told > me they will not support 2 Windows compilers. They will only > support the mingw64 project. They refuse to take patches to make > mingw (from mingw.org) work. Some of the projects have been > downright nasty when I send patches to them to add support for > mingw (mingw.org version). I'm one of the "not support 2 Windows compilers" people. Whatever i do, i aim at mingw-w64 compatibility. That said, i do tend to accept (whenever i am the one making the decision, which isn't very often really) mingw.org-compatibility patches, if they aren't intrusive. >> The situation was frustrating for Mr Lavavej too. So he made his >> own very good MingW (x64 native) light-weight distro; [1] >> http://nuwen.net/mingw.html >> >> So when I finally upgrade to Win8.1 (with a i7 CPU?), I will use >> his distro to target x64-native. And not the rather confusing >> distro from http://mingw-w64.sourceforge.net/. > > Thanks for the information on this. I'm personally still targeting > 32 bit even though I have a 64 bit platform to work with because > some of my machines still use 32 bit. However, I know some people > who are targeting 64 bit. I'm still using i686 as well, though for other reasons (contrary to popular belief, building correct x86_64 versions of software packages requires more than changing the toolchain for an x86_64 one (and changing compiler flags)). I also maintain my own packages. That said, i don't see a reason to distance myself from mingw-w64, since i tend to fix up their stuff whenever needed, and i freely exchange patches with current mingw-w64 package maintainers. And i'm not sure what the "confusing distro" is being referred to (this might be a reference to cross-compiler'y layout of the toolchain OR to multilib toolchain - in which case i agree, i prefer to stick to native toolchains). - -- O< ascii ribbon - stop html email! - www.asciiribbon.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJS/9YYAAoJEOs4Jb6SI2Cw3hoH/j/F9x9J0zSWzxMQ9lpBj7S/ tE/I7teOixMLVcTdlwGa3rpvNBf+mYEnoHvF/oMce2p9TarwlL+qT2Y1f7fUTQss n+loag/lhPDhjCxzm7yW4dhyB79eLIRGs5+EEolGuaIIIiCk4pCqbThC4nHzPjx6 bcM+M6LJWKWhc4RQzktoUi9CN0t2OkDzjrQj0dX9hJaRBqr9aOWTImJ6sMhQeI2S 81Ni8eSYRm6OYZbCujqxwNRjP217hFzGOsk5FfxCz+Len218q31h9Gi5bi4QF1Mz Q1HgHhwE87u3GOCiXHLxiQMzdU4hZkjU8UErukgX07W1V00oseDVjvmbWkzj864= =Wvq3 -----END PGP SIGNATURE----- |
From: KD <kd...@gm...> - 2014-02-15 21:27:08
|
The mingw64 project can target both 32 bit and 64 bit windows. And in my eyes, and several others, it is the definitive cross platform compiler, as it can target both bit widths. While it may be true that on 64 bit systems some applications, if not all, when compiled for 32 bit run faster than their 64 bit counterpart, the reality of the matter is that all platforms are moving towards ubiquitous 64 bit widths. This is the reason your seeing a lot of projects supporting mingw64 in favor of mingw (as mingw64 was created due to mingw's refusal to support 64 bit). While it's tempting to write off a lot of open source projects simply because they do not support mingw, mingw64 is easily obtainable, reliable, and industry proven. And that, honestly, is also the reason for their enmity towards your patches, as they would target mingw if they wanted to. On Sat, Feb 15, 2014 at 1:40 PM, <ml...@di...> wrote: > Gisle Vanem wrote: > > It's kind of confusing situation, yes. I cannot advice much on making > > mingw.org more acceptable for projects. But the resentment toward > > old-school MingW is probably partly because of the somewhat confusing > > situation with how both projects define '__MINGW32__'? > > I'm not seeing an issue with projects having trouble defining #ifdefs > between the two versions. Projects have straight out told me they will > not support 2 Windows compilers. They will only support the mingw64 > project. They refuse to take patches to make mingw (from mingw.org) work. > Some of the projects have been downright nasty when I send patches to > them to add support for mingw (mingw.org version). > > It's hard enough porting Open Source projects from other platforms to > Windows and getting them to build. Having to worry about whether your > using an "accepted" Windows compiler for each particular project makes > matters even worse. > > Would like to hear from others encountering this issue. Please let me > know if you have any techniques for working around it. Thanks. > > I'm building several Open Source libraries and programs from source on > several platforms including Windows. So far, when I run into a situation > like this, I've written the project off my list of projects to build and > looked for a more accomodating cross-platform project. > > > The situation was frustrating for Mr Lavavej too. So he made his own very > > good MingW (x64 native) light-weight distro; > > [1] http://nuwen.net/mingw.html > > > > So when I finally upgrade to Win8.1 (with a i7 CPU?), I will use his > > distro to target x64-native. And not the rather confusing distro from > > http://mingw-w64.sourceforge.net/. > > Thanks for the information on this. I'm personally still targeting 32 bit > even though I have a 64 bit platform to work with because some of my > machines still use 32 bit. However, I know some people who are targeting > 64 bit. > > Sincerely, > Laura > http://www.distasis.com/cpp > > > > ------------------------------------------------------------------------------ > Android apps run on BlackBerry 10 > Introducing the new BlackBerry 10.2.1 Runtime for Android apps. > Now with support for Jelly Bean, Bluetooth, Mapview and more. > Get your Android app in front of a whole new audience. Start now. > > http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list > etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > Also: mailto:min...@li...?subject=unsubscribe > -- ¯`°²º¤æ=.KD.=椺²°`¯ |