[Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread jan van katwijk
-- Forwarded message -- From: Erik van Pienbroek Date: 2012/7/4 Subject: Re: [Mingw-w64-public] cross compiling with static Qt libraries To: mingw-w64-public@lists.sourceforge.net jan van katwijk schreef op wo 04-07-2012 om 11:41 [+0200]: > x86_64-w64-mingw32-g++ -static -Wl,-s -

[Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread jan van katwijk
-- Forwarded message -- From: Erik van Pienbroek Date: 2012/7/4 Subject: Re: [Mingw-w64-public] cross compiling with static Qt libraries To: mingw-w64-public@lists.sourceforge.net jan van katwijk schreef op wo 04-07-2012 om 11:41 [+0200]: > x86_64-w64-mingw32-g++ -static -Wl,-s -

Re: [Mingw-w64-public] cross compiling with static Qt libraries

2012-07-04 Thread Erik van Pienbroek
jan van katwijk schreef op wo 04-07-2012 om 11:41 [+0200]: > I installed Fedora 17 and the - excellent - cross compilation tools > for mingw64. It was surprisingly simple to > generate an executable using dynamically bound libs, however, when > trying to create an executable with static binding > f

Re: [Mingw-w64-public] cross compiling with static Qt libraries

2012-07-04 Thread Erik van Pienbroek
jan van katwijk schreef op wo 04-07-2012 om 11:41 [+0200]: > x86_64-w64-mingw32-g++ -static -Wl,-s -Wl,-subsystem,console -mthreads > -o release/spectrum-viewer.exe object_script.spectrum-viewer.Release > -L'/usr/x86_64-w64-mingw32/sys-root/mingw/lib' > /home/jan/cross-compiling/dll_64/libfftw3-3.

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Ozkan Sezer
On 7/4/12, Kai Tietz wrote: > 2012/7/4 Ozkan Sezer : >> On 7/4/12, Kai Tietz wrote: >>> 2012/7/4 Ozkan Sezer : On 7/4/12, Kai Tietz wrote: > 2012/7/4 Tristan Gingold : >> Hi, >> >>> as you patch was applied to gcc's repository will you sent an >>> updated >>> version

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Kai Tietz
2012/7/4 Ozkan Sezer : > On 7/4/12, Kai Tietz wrote: >> 2012/7/4 Ozkan Sezer : >>> On 7/4/12, Kai Tietz wrote: 2012/7/4 Tristan Gingold : > Hi, > >> as you patch was applied to gcc's repository will you sent an updated >> version of your patch for setjmp.h header? > >

Re: [Mingw-w64-public] Strange behavior of snwprintf() function

2012-07-04 Thread xunxun
于 2012/7/4 23:46, niXman 写道: > The following code gives the right result when compiled without > defined __USE_MINGW_ANSI_STDIO macro. > But, if __USE_MINGW_ANSI_STDIO macro is defined - the result is 6. > Why? > > code: > #include > int main() { > wchar_t buf[2]; > int len = snwprintf(b

[Mingw-w64-public] Strange behavior of snwprintf() function

2012-07-04 Thread niXman
The following code gives the right result when compiled without defined __USE_MINGW_ANSI_STDIO macro. But, if __USE_MINGW_ANSI_STDIO macro is defined - the result is 6. Why? code: #include int main() { wchar_t buf[2]; int len = snwprintf(buf, sizeof(buf) / 2, L"world!"); printf("%d\n"

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Ozkan Sezer
On 7/4/12, Kai Tietz wrote: > 2012/7/4 Ozkan Sezer : >> On 7/4/12, Kai Tietz wrote: >>> 2012/7/4 Tristan Gingold : Hi, > as you patch was applied to gcc's repository will you sent an updated > version of your patch for setjmp.h header? Sure. I was writing a mail about

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Kai Tietz
2012/7/4 Ozkan Sezer : > On 7/4/12, Kai Tietz wrote: >> 2012/7/4 Tristan Gingold : >>> Hi, >>> as you patch was applied to gcc's repository will you sent an updated version of your patch for setjmp.h header? >>> >>> Sure. I was writing a mail about that, but you were faster. >>> Do

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Tristan Gingold
On Jul 4, 2012, at 3:26 PM, Ozkan Sezer wrote: > On 7/4/12, Kai Tietz wrote: >> 2012/7/4 Tristan Gingold : >>> Hi, >>> as you patch was applied to gcc's repository will you sent an updated version of your patch for setjmp.h header? >>> >>> Sure. I was writing a mail about that, but

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Ozkan Sezer
On 7/4/12, Kai Tietz wrote: > 2012/7/4 Tristan Gingold : >> Hi, >> >>> as you patch was applied to gcc's repository will you sent an updated >>> version of your patch for setjmp.h header? >> >> Sure. I was writing a mail about that, but you were faster. >> >>> Do you think we should use for older

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Kai Tietz
2012/7/4 Tristan Gingold : > Hi, > >> as you patch was applied to gcc's repository will you sent an updated >> version of your patch for setjmp.h header? > > Sure. I was writing a mail about that, but you were faster. > >> Do you think we should use for older gcc-versions - not having the >> fixed

[Mingw-w64-public] Fwd: Fwd: cross compiling with static Qt libraries !!! Solved !!!

2012-07-04 Thread jan van katwijk
It was my own stupidity, not having set the right option to CONFIG in the pro file. Anyway thanks for the replies best jan -- Forwarded message -- From: jan van katwijk Date: 2012/7/4 Subject: Fwd: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries To: mingw-w64-pu

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Tristan Gingold
Hi, > as you patch was applied to gcc's repository will you sent an updated > version of your patch for setjmp.h header? Sure. I was writing a mail about that, but you were faster. > Do you think we should use for older gcc-versions - not having the > fixed frame-pointer builtin - still __mingw

Re: [Mingw-w64-public] Bug in setjmp.h on win64 + SEH

2012-07-04 Thread Kai Tietz
Hello Tristan, as you patch was applied to gcc's repository will you sent an updated version of your patch for setjmp.h header? Do you think we should use for older gcc-versions - not having the fixed frame-pointer builtin - still __mingw_getsp instead? Regards, Kai -

[Mingw-w64-public] Fwd: Fwd: cross compiling with static Qt libraries

2012-07-04 Thread jan van katwijk
-- Forwarded message -- From: xunxun Date: 2012/7/4 Subject: Re: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries To: mingw-w64-public@lists.sourceforge.net Cc: jan van katwijk 于 2012/7/4 18:35, jan van katwijk 写道: May be this is the wrong list, do not know, bu

Re: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread xunxun
于 2012/7/4 18:35, jan van katwijk 写道: > May be this is the wrong list, do not know, but it seems to me that > QtCore and QtGui need a lot of > windows-related libs, such as ole32 and gdi32, and a lot more, but I > cannot find which ones. > > The second issue is indeed the way the makefile is gene

Re: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread Kai Tietz
2012/7/4 xunxun : > And, Kai > > Should we add -lole32 and -lgdi32 to gcc's internal specs? > This may avoid the issue. > > -- > Best Regards, > xunxun > Hmm, this seems not to be the right thing. gdi32.dll will be automatically added if option '-mwindows' is specified. This makes sense as other

Re: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread jan van katwijk
May be this is the wrong list, do not know, but it seems to me that QtCore and QtGui need a lot of windows-related libs, such as ole32 and gdi32, and a lot more, but I cannot find which ones. The second issue is indeed the way the makefile is generated and the order in which the libraries appear i

Re: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread xunxun
And, Kai Should we add -lole32 and -lgdi32 to gcc's internal specs? This may avoid the issue. -- Best Regards, xunxun -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security an

Re: [Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread xunxun
于 2012/7/4 18:12, jan van katwijk 写道: > Thanx so far. It seems that the qmake does not generate a right order > for the libs to be linked. > When adding LIBS += -lole32 -lgdi32 to the ".pro" file, the -lole32 > -lgdi32 appears in front > of the Qtlibs and they will not find the symbols. When man

[Mingw-w64-public] Fwd: cross compiling with static Qt libraries

2012-07-04 Thread jan van katwijk
Thanx so far. It seems that the qmake does not generate a right order for the libs to be linked. When adding LIBS += -lole32 -lgdi32 to the ".pro" file, the -lole32 -lgdi32 appears in front of the Qtlibs and they will not find the symbols. When manually adding the libs to the line, these symbols a

Re: [Mingw-w64-public] cross compiling with static Qt libraries

2012-07-04 Thread xunxun
于 2012/7/4 17:41, jan van katwijk 写道: Dear list I have an SDR application with Qt developed under Linux (Fedora/ubuntu). It does run under windows (vista/w7) using mingw/Qt. I am preparing a windows distribution with - as much as possible - statically bound libraries I installed Fedora 17 and

Re: [Mingw-w64-public] cross compiling with static Qt libraries

2012-07-04 Thread Kai Tietz
Hi, your issue is a missing import-library, or it placed at wrong place on command-line. For StringFromGUID you need to add -lole32 library. For the GetDeviceCaps import you need to specify -lgdi32. Regards, Kai -- Liv

[Mingw-w64-public] cross compiling with static Qt libraries

2012-07-04 Thread jan van katwijk
Dear list I have an SDR application with Qt developed under Linux (Fedora/ubuntu). It does run under windows (vista/w7) using mingw/Qt. I am preparing a windows distribution with - as much as possible - statically bound libraries I installed Fedora 17 and the - excellent - cross compilation tools