On 5/12/2012 03:15, Whitequill Riclo wrote:
> On Fri, May 11, 2012 at 2:51 PM, Whitequill Riclo
> wrote:
>
>>
>> On Thu, May 10, 2012 at 6:14 PM, JonY wrote:
>>
>>> On 5/11/2012 03:14, Whitequill Riclo wrote:
On Sun, Feb 19, 2012 at 12:27 AM, Whitequill Riclo
wrote:
> thanx, I'
On 5/11/2012 9:10 AM, Ruben Van Boxem wrote:
> Yes, TDM's toolchain is a native build. but please don't use it, it's
> old (by now) and as you can see has installation problems
:(
With these two frankly unfounded generalizations, you may be scaring off
quite a few innocent readers who might hav
Op 11 mei 2012 20:32 schreef "Erik van Pienbroek"
het volgende:
>
> Ruben Van Boxem schreef op vr 11-05-2012 om 17:10 [+0200]:
>
> > Remember to add the -qt-style-windows* options when you call Qt's
> > configure or you'll get ugly Windows 95 style GUI's for all you Qt
> > programs.
>
> If your mk
MARTIN Pierre schreef op vr 11-05-2012 om 20:42 [+0200]:
> All right, but apart from creating your custom mkspec, did you need any
> particular patching of the Qt source?
In Fedora we applied various patches to Qt to fix some issues which
aren't resolved upstream yet or are Fedora specific. It sh
Dear Erik,
First of all, i really appreciate you taking time to answer me.
> The qmake build system doesn't work with build triplets, but with
> so-called mkspecs profiles. These profiles are located in the mkspecs
> folder which is part of the Qt source tarball.
Right.
> If you open the file mk
Ruben Van Boxem schreef op vr 11-05-2012 om 17:10 [+0200]:
> Remember to add the -qt-style-windows* options when you call Qt's
> configure or you'll get ugly Windows 95 style GUI's for all you Qt
> programs.
If your mkspecs name starts with "win32-g++" then these
qt-style-windows* options will be
MARTIN Pierre schreef op vr 11-05-2012 om 15:58 [+0200]:
> Now, i am trying to configure Qt 4.8.1 to compile it with MinGW-w64 (i
> am willing to compile it on windows XP 32 bits for Windows XP 32
> bits). But my problem right now is that i can't seem to understand how
> to give it the build tripl
On Fri, May 11, 2012 at 6:15 PM, Ruben Van Boxem
wrote:
> 2012/5/11 MARTIN Pierre
>>
>> > Yes, you will, but depending on how you build them, you'll need to point
>> > the project's build infrastructure to find the Qt you've built. There's
>> > nothing special about MSYS, it's only an emulation o
> Take a look at GNUWin32 they have a lot of the programs you'd want, for use
> with cmd. The shell remains the same old non-functional cruft, but you get
> ls, file, find, etc... Just remember GNU find is not Windows find, and some
> stuff might expect the Windows version.
Thanks for the tip!--
2012/5/11 MARTIN Pierre
> > Yes, you will, but depending on how you build them, you'll need to point
> the project's build infrastructure to find the Qt you've built. There's
> nothing special about MSYS, it's only an emulation of a POSIX shell on top
> of Windows.
> Perfect. Thanks Ruben :) Just
> Yes, you will, but depending on how you build them, you'll need to point the
> project's build infrastructure to find the Qt you've built. There's nothing
> special about MSYS, it's only an emulation of a POSIX shell on top of Windows.
Perfect. Thanks Ruben :) Just for my personal information,
2012/5/11 MARTIN Pierre
> > No, it's not related to the toolchain. This is Qt's configure not
> working on MSYS. Specifically, -DUNICODE is missing from the compiler
> options.
> It's working with SeZero's build. i'm really wondering what's different in
> his build.
>
> > I must *strongly* urge
> No, it's not related to the toolchain. This is Qt's configure not working on
> MSYS. Specifically, -DUNICODE is missing from the compiler options.
It's working with SeZero's build. i'm really wondering what's different in his
build.
> I must *strongly* urge you to try building Qt from cmd ins
2012/5/11 Kai Tietz
> 2012/5/11 MARTIN Pierre :
> > The last toolchain i have downloaded is the one from TDM's. i'm trying
> to compile Qt 4.8.1 with it, and it fails where SeZero's build was
> successfull.
> > The error message i get is when compiling QMake (Which takes place in
> the ./configur
> Yes, a Linux plus Wine (64-bit or 32-bit) is absolutely an alternative
> to cygwin/msys. It has also the advantage of the speed of Linux.
> There is also a 64-bit Wine version, not sure if it is available for
> MAC, too. I am using on my Linux-box Wine for running testsuites. Eg
> testsuite ru
Kai,
>> Creating qmake. Please wait...
>> g++ -c -o project.o -DQMAKE_OPENSOURCE_EDITION -g -I. -Igenerators
>> -Igenerators/unix -Igenerators/win32 -Igenerators/ma
>> c -Igenerators/symbian -Igenerators/integrity
>> -I/QtSDK/Desktop/Qt/4.8.1/i686-w64-mingw32/include -I/QtSDK/Desktop/Qt/4.8
>>
2012/5/11 MARTIN Pierre :
> The last toolchain i have downloaded is the one from TDM's. i'm trying to
> compile Qt 4.8.1 with it, and it fails where SeZero's build was successfull.
> The error message i get is when compiling QMake (Which takes place in the
> ./configure part):
>
> Creating qmake.
2012/5/11 MARTIN Pierre :
> Hello again :)
>
> As my easiest questions were answered flawlessly, now i am going to ask you
> something that might interest you more.
> I primarily do my coding on my Mac. i choose the Qt framework because my
> projects have to run exactly the same on Windows, Linux
The last toolchain i have downloaded is the one from TDM's. i'm trying to
compile Qt 4.8.1 with it, and it fails where SeZero's build was successfull.
The error message i get is when compiling QMake (Which takes place in the
./configure part):
Creating qmake. Please wait...
g++ -c -o project.o
Hello again :)
As my easiest questions were answered flawlessly, now i am going to ask you
something that might interest you more.
I primarily do my coding on my Mac. i choose the Qt framework because my
projects have to run exactly the same on Windows, Linux and Mac OSX (At least i
use Qt for
>> - When using the Europe -> France -> Free mirror, the package
>> make-3.82-mingw32-bin.tar.lzma cannot be found on the server (404 type
>> error). Is Dragon part of this list, or is it another project mailing list i
>> shall subscribe to to report the problems i encounter?
> Hmm, I heard that so
2012/5/11 MARTIN Pierre :
> Dear Ruben, dear list readers,
>
>> I suggest using a native MinGW-w64 toolchain to build Qt. Qt does not
>> support cross-compiling (just look at the OpenSuse or Fedora mingw-w64 Qt
>> package build scripts: they patch the hell out of Qt's build
>> infrastructure).
>>
>
2012/5/11 MARTIN Pierre
> Dear Ruben, dear list readers,
>
> I suggest using a native MinGW-w64 toolchain to build Qt. Qt does not
>> support cross-compiling (just look at the OpenSuse or Fedora mingw-w64 Qt
>> package build scripts: they patch the hell out of Qt's build
>> infrastructure).
>>
>>
Dear Ruben, dear list readers,
>> I suggest using a native MinGW-w64 toolchain to build Qt. Qt does not
>> support cross-compiling (just look at the OpenSuse or Fedora mingw-w64 Qt
>> package build scripts: they patch the hell out of Qt's build infrastructure).
>
> Ah! But i *am* using a native
2012/5/11 MARTIN Pierre
> Dear Ruben,
>
> First, thank you very much for your kind help.
>
> Is there anyone here successfull in compiling Qt 4.8.1 with MinGW-w64
>> using MSys? If yes, how?
>>
>
> No, it's not intended to be built from MSYS on windows. It might work, but
> is not recommended (by
Dear Ruben,
First, thank you very much for your kind help.
> Is there anyone here successfull in compiling Qt 4.8.1 with MinGW-w64 using
> MSys? If yes, how?
>
> No, it's not intended to be built from MSYS on windows. It might work, but is
> not recommended (by me nor Nokia). This problem thou
Hallo Kai,
> sure there are a lot of people building Qt by using mingw-w64 (for
> 32-bit and 64-bit version).
i would really be interested to know about their setup / configure options, as
the automated MinGw binary doesn't works for me.
Please note that i just have downloaded SeZero MinGW build,
2012/5/11 MARTIN Pierre
> Dear list readers,
>
> As you might remember, i have been playing around with MinGW-w64 on MSys
> to see if it could be of a good replacement for compiling on / for windows.
> i finally have dropped the migration, as i was seriously lacking some
> research time.
>
> Now
Hallo,
sure there are a lot of people building Qt by using mingw-w64 (for
32-bit and 64-bit version).
Have you checked on our Wiki the following links?
https://sourceforge.net/apps/trac/mingw-w64/wiki/MSYS
https://sourceforge.net/apps/trac/mingw-w64/wiki/BuildingQt
Regards,
Kai
-
Dear list readers,
As you might remember, i have been playing around with MinGW-w64 on MSys to see
if it could be of a good replacement for compiling on / for windows.
i finally have dropped the migration, as i was seriously lacking some research
time.
Now that i have a bit time for me again, i
2012/5/11 Earnie Boyd :
> On Thu, May 10, 2012 at 3:57 PM, David Froger wrote:
>>> Sure, you are using here within cygwin a native gcc. Of course it
>>> doesn't support cygwin's pathname.
>>> If you want to use cygwin, then please use the mingw-w64 package
>>> provided within cygwin's setup.
>>
>
2012/5/11 Earnie Boyd :
> On Fri, May 11, 2012 at 2:20 AM, Ruben Van Boxem
> wrote:
>> Op 11 mei 2012 03:50 schreef "tomdean" het volgende:
>>
>>
>>>
>>> On 5/10/2012 6:00 PM, Luis Lavena wrote:
>>> > Use gcc -mwindows, by default it will create a console application.
>>> > See gcc --target-help
Excerpts from Earnie Boyd's message of ven. mai 11 15:00:37 +0200 2012:
> On Thu, May 10, 2012 at 3:57 PM, David Froger wrote:
> >> Sure, you are using here within cygwin a native gcc. Of course it
> >> doesn't support cygwin's pathname.
> >> If you want to use cygwin, then please use the mingw-w
On Thu, May 10, 2012 at 3:57 PM, David Froger wrote:
>> Sure, you are using here within cygwin a native gcc. Of course it
>> doesn't support cygwin's pathname.
>> If you want to use cygwin, then please use the mingw-w64 package
>> provided within cygwin's setup.
>
> Thanks for your reply!
>
> I u
On Fri, May 11, 2012 at 2:20 AM, Ruben Van Boxem
wrote:
> Op 11 mei 2012 03:50 schreef "tomdean" het volgende:
>
>
>>
>> On 5/10/2012 6:00 PM, Luis Lavena wrote:
>> > Use gcc -mwindows, by default it will create a console application.
>> > See gcc --target-help
>> I am using 'g++ -I. -lgdi32 -lco
35 matches
Mail list logo
