2013/1/31 Zach Thibeau:
> The main reasons msvc generates smaller binaries in general is that it does
> optimizations better than GCC currently, but hopefully that can change soon
Not much better...
Besides, the reason not in it.
--
Regards,
niXman
___________________________________________________
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingwbuilds/
___________________________________________________
Another online IDE: http://liveworkspace.org/

> -----Original Message-----
> From: niXman [mailto:i.nixman@...]
> Sent: Thursday, January 31, 2013 3:48 PM
> To: Koehne Kai; Mingw-w64-public@...; mingwbuilds-
> users@...
> Subject: Re: [Mingwbuilds-users] Qt 5.0.1 binary packages with MinGW-
> builds toolchain
>
> 2013/1/31 Koehne Kai:
> > Hi there,
> >
> > The qt-project and Digia just released Qt 5.0.1 binary installer for MinGW!
> >
> > http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/
> >
> > The binary is compiled with and comes with the x32-4.7.2-release-posix-
> sjlj-rev8.7z toolchain from MinGW-builds. Quite a lot of you have been
> helping to get this going, so thanks a lot and be proud :)
> Tell me please, why the 64-bit build is missing?
No special reason apart from the fact that we considered 32 bit to be more important. Note that we're also still missing MSVC 64 bit packages, too ... it's a matter of resources, both in the build & test system and when it comes to release testing etc. We might consider shipping a 64 bit version in an upcoming installer, let's see what the feedback says.
But I'm compiling locally with the 64 bit toolchain too, without any troubles.
Regards
Kai

2013/1/31 Koehne Kai:
> Hi there,
>
> The qt-project and Digia just released Qt 5.0.1 binary installer for MinGW!
>
> http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/
>
> The binary is compiled with and comes with the x32-4.7.2-release-posix-sjlj-rev8.7z toolchain from MinGW-builds. Quite a lot of you have been helping to get this going, so thanks a lot and be proud :)
Tell me please, why the 64-bit build is missing?
--
Regards,
niXman
___________________________________________________
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingwbuilds/
___________________________________________________
Another online IDE: http://liveworkspace.org/

2013/1/31 Koehne Kai:
> Hi there,
>
> The qt-project and Digia just released Qt 5.0.1 binary installer for MinGW!
>
> http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/
>
> The binary is compiled with and comes with the x32-4.7.2-release-posix-sjlj-rev8.7z toolchain from MinGW-builds. Quite a lot of you have been helping to get this going, so thanks a lot and be proud :)
It is excellent!
But tell me please, why the archive for MinGW in the size is almost
twice more than all other builds? Is it normal?
--
Regards,
niXman
___________________________________________________
Dual-target(32 & 64-bit) MinGW compilers for 32 and 64-bit Windows:
http://sourceforge.net/projects/mingwbuilds/
___________________________________________________
Another online IDE: http://liveworkspace.org/

Hi there,
The qt-project and Digia just released Qt 5.0.1 binary installer for MinGW!
http://blog.qt.digia.com/blog/2013/01/31/qt-5-0-1-released/
The binary is compiled with and comes with the x32-4.7.2-release-posix-sjlj-rev8.7z toolchain from MinGW-builds. Quite a lot of you have been helping to get this going, so thanks a lot and be proud :)
You rock
Kai

Hello Lists!
It looks like I've managed to port QuickFIX to mingw-w64.
I haven't run the unit tests (because I didn't have the energy to port
UnitTest++), and I haven't run the acceptance tests (because I didn't
want to deal with the ruby dependency), but I have built a relatively
simple QuickFIX application using my ported library.
Its socket connections work, it runs multiple threads, and it parses
its xml data dictionaries, so the three most platform-dependent pieces
of the system seem, at least on the surface, to be working.
I ended up going with libxml2 (because mingw-w64's msmxl2 seemed
to have some bugs, and, in any event, QuickFIX lists MSXML3 as its
dependency). I used the pre-built mingw-w64 libxml2 from:
http://www.stats.ox.ac.uk/pub/Rtools/R215x.html
that Prof Brian Ripley suggested in an earlier thread. I had had
some concern that a version mismatch between the compiler
used to build libxml2 and the version I'm using might cause an
incompatibility, but then I recalled that libxml2 is a c library, rather
than c++ where such abi breakage would have been more likely.
Most of the porting work involved selectively changing various
#ifdef's dependent on _MSC_VER (not defined by mingw-w64)
to use _WIN32 instead. There were some minor fixes to
microsoft stuff and a little bit of 64-bit tweakage.
As I said, I don't have any reason to expect my current version
to be bug free, but the basic functionality is there, and I haven't
seen anything break yet.
Thanks for folks suggestions that helped get me going.
Best regards.
K. Frank

Hi,
Using mingw32-gcc-4.7.2-2.fc18.x86_64 &
mingw32-crt-2.0.999-0.15.trunk.20121110.fc18.noarch
I am wondering against which library I should be linking, -lsetupapi
doesn't seem to have the symbol:
undefined reference to `_imp__SetupUninstallOEMInfW@...'
Thanks for your help!
--
Marc-André Lureau

On Wed, Jan 23, 2013 at 3:22 AM, Ruben Van Boxem wrote:
> 2013/1/23 Xiaofan Chen
>>
>> On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels wrote:
>> >
>> > and, alas, microsoft has made sp2 unavailable and xp next year is
>> > support
>> > EOL except for embedded. so SP1 users (like me) are out of luck unless
>> > they
>> > have already downloaded and burned a copy of SP2 and SP3. after EOL,
>> > updates
>> > will no longer be available from http://windowsupdate.microsoft.com,
>> > just
>> > like with windows 9x/me/2000.
>>
>> Are you still using Windows XP SP1? If that is the case, I am wondering
>> how you can stop those worms spreading to your computer unless your
>> XP SP1 computer is isolated from the Internet.
>>
>> I still remember the famous W32.Blaster worm affected many university
>> PCs back in 2003.
>
>
> Exactly. I don't see the need for anything to support Windows version
> whatever past its EOL. That's just a pain the shenanigans with no merit
> whatsoever. That being said, XP SP1 is stone age, where XP SP3 (!) is more
> like... iron age. Note this isn't at all the official MinGW-w64 point of
> view, but my personal opinion on old and deprecated software.
Regardless, the header set can be controlled as Microsoft does with
NTDDI_VERSION. See
http://msdn.microsoft.com/en-us/library/windows/desktop/aa383745(v=vs.85).aspx
for reference.
In this case NTDDI_VERSION would be >= 0x05010300 before _vswprintf is
declared. The user would need to set NTDDI_VERSION to the minimum
supported value for his software. The user of that software would
need to ensure his system meets that minimum standard.
--
Earnie
-- https://sites.google.com/site/earnieboyd

2013/1/23 Xiaofan Chen <xiaofanc@...>
> On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels <jmichae3@...> wrote:
> >
> > and, alas, microsoft has made sp2 unavailable and xp next year is
> support
> > EOL except for embedded. so SP1 users (like me) are out of luck unless
> they
> > have already downloaded and burned a copy of SP2 and SP3. after EOL,
> updates
> > will no longer be available from http://windowsupdate.microsoft.com,
> just
> > like with windows 9x/me/2000.
>
> Are you still using Windows XP SP1? If that is the case, I am wondering
> how you can stop those worms spreading to your computer unless your
> XP SP1 computer is isolated from the Internet.
>
> I still remember the famous W32.Blaster worm affected many university
> PCs back in 2003.
>
Exactly. I don't see the need for anything to support Windows version
whatever past its EOL. That's just a pain the shenanigans with no merit
whatsoever. That being said, XP SP1 is stone age, where XP SP3 (!) is more
like... iron age. Note this isn't at all the official MinGW-w64 point of
view, but my personal opinion on old and deprecated software.
Ruben
>
> --
> Xiaofan
>
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@...
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

On Wed, Jan 23, 2013 at 2:58 PM, Jim Michaels <jmichae3@...> wrote:
>
> and, alas, microsoft has made sp2 unavailable and xp next year is support
> EOL except for embedded. so SP1 users (like me) are out of luck unless they
> have already downloaded and burned a copy of SP2 and SP3. after EOL, updates
> will no longer be available from http://windowsupdate.microsoft.com, just
> like with windows 9x/me/2000.
Are you still using Windows XP SP1? If that is the case, I am wondering
how you can stop those worms spreading to your computer unless your
XP SP1 computer is isolated from the Internet.
I still remember the famous W32.Blaster worm affected many university
PCs back in 2003.
--
Xiaofan

On Wed, Jan 23, 2013 at 2:50 PM, Jim Michaels <jmichae3@...> wrote:
> just what is TDM-GCC? I have seen this mentioned a number
> of times, but I haven't seen a folder for it in the mingw-w64 folder tree
> that I remember.
>
> my guess is it's some sort of code name for something.
>
TDM-GCC is a disro of MinGW.org and MinGW-w64.
http://tdm-gcc.tdragon.net/
I consider it to be one of the more mature MinGW-w64 distributions
out there. I use MinGW.org's official distribution and not TDM's, but
I used to only use TDM's build when it comes to MinGW-w64. Now
there are more choices.
In fact, for libusbK project, we only officially support TDM's
MinGW-w64 distribution for the GCC example build.
http://code.google.com/p/usb-travis/source/browse/trunk/libusbK/examples/GNUmakefile
--
Xiaofan

and, alas, microsoft has made sp2 unavailable and xp next year is support EOL except for embedded. so SP1 users (like me) are out of luck unless they have already downloaded and burned a copy of SP2 and SP3. after EOL, updates will no longer be available from http://windowsupdate.microsoft.com, just like with windows 9x/me/2000.
http://support.microsoft.com/lifecycle/search/?sort=PN&alpha=WINDOWS+XP&Filter=FilterNO
Jim Michaels
________________________________
From: Kai Tietz <ktietz70@...>
To: mingw-w64-public@...
Sent: Monday, January 21, 2013 5:07 AM
Subject: Re: [Mingw-w64-public] Suggestion for FAQ Re _vswprintf and msvcrt.dll on XP SP1
>2013/1/21 Jacek Caban <jacek@...>:
>> On 01/21/13 13:39, JonY wrote:
>>> On 1/21/2013 09:43, Herb Thompson wrote:
>>>> Q: Why do some 32-bit MinGW-w64 applications fail with '... _vswprintf
>>>> could not be located in the dynamic link library msvcrt.dll' on Windows
>>>> XP SP1?
>>>>
>>>> A: For C++, MinGW-w64 implements 'vswprintf (wchar_t *__stream, const
>>>> wchar_t *__format, __builtin_va_list __local_argv)' as a call to
>>>> '_vswprintf'. Older versions of msvcrt.dll, like the version in XP SP1,
>>>> do not include '_vswprintf'. A workaround for this is to compile any
>>>> C++ libraries and applications that use 'vswprintf' (with the preceding
>>>> signature) with -D__USE_MINGW_ANSI_STDIO. For example, to build the
>>>> wxWidgets library for applications to be deployed on XP SP1, build
>>>> wxWidgets with the following command line:
>>>> > mingw32-make -f makefile.gcc CPPFLAGS="-D__USE_MINGW_ANSI_STDIO"
>>> Done as
>>> https://sourceforge.net/apps/trac/mingw-w64/wiki/_vswprintf%20missing.
>>>
>>> Thanks.
>>>
>>> I've also added a caveat section on the side effects of using
>>> __USE_MINGW_ANSI_STDIO.
>>
>> Well, IMO we should fix bugs instead of documenting them... I may look
>> at this, but I'm not sure when I will find time for that.
>>
>> Jacek
>
>Well, in general I agree. We might should do same hack (for older
>msvcrt versions) as we do for vscanf (as example).
>
>Cheers,
>Kai
>
>------------------------------------------------------------------------------
>Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>MVPs and experts. SALE $99.99 this month only -- learn more at:
>http://p.sf.net/sfu/learnmore_122412
>_______________________________________________
>Mingw-w64-public mailing list
>Mingw-w64-public@...
>https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
>