From: Ruben V. B. <van...@gm...> - 2011-05-09 07:34:15
|
Op 9 mei 2011 00:16 schreef "K. Frank" <kfr...@gm...> het volgende: > > Hi Ruben! > > On Sun, May 8, 2011 at 2:15 PM, Ruben Van Boxem wrote: > > Op 8 mei 2011 16:21 schreef "K. Frank" het volgende: > >> Hello Ruben! > >> ... > >> (I''ve taken the liberty of cross-posting this to the Qt list, because I > >> have a question about Qt; see below.) > >> > >> On Sun, May 8, 2011 at 5:47 AM, Ruben Van Boxem wrote: > >> > I have released an update to my 4.6.1 prerelease toolchain. > >> > ... > >> > There is both a 32-bit and 64-bit build, but there are some minor > >> > issues: > >> > ... > >> > Therefore I have resorted to two native builds, one 32-bit targetting > >> > 32-bit, the other 64-bit targetting 64-bit Windows. > >> > ... > >> You mention QtCreator, so please let me ask about any known issues > >> with Qt. > >> > >> I have been considering upgrading to g++ version 4.6 (from 4.4.1) and > >> Qt version 4.7 (from 4.6.1), not for any specific technical reason, but > >> just to stay "up to date," so to speak. (I would be happy to use either > >> the 32-bit or 64-bit version, or maybe both, just for fun.) > >> ... > >> What do people think? Is g++ 4.6.1 (and Ruben's personal build, in > >> particular) likely to work with Qt 4.7? Has anyone actually tried it and > >> knows that it works? Or knows that is works, but with some manageable > >> work-arounds? Or knows that it basically doesn't work? > > > > I'm quite confident that it will "just work". Modifying the mkspec files to > > use lto produces a bad Webkit, but this is not important for you. Lto is > > broken in my build, so forget about this. > > I'm not particularly focused on optimization, so I wouldn't be enabling > lto. (I'm also not using Webkit.) > > > On the other hand, why rebuild what you already have? Only reason would be > > optimization, but I wouldn't bother. You should be able to use the new GCC > > version to link the older libraries. Just use the new compiler for your > > current project, using prebuilt libs. > > My current "everyday" installation of Qt (and some other small libraries) > was built with a tdm mingw32 gcc build: > > g++ --version: g++ (TDM-2 mingw32) 4.4.1 > > I just sort of assumed that I wouldn't be able to mix my current > (tdm 4.4.1) Qt libraries with code compiled with the new compiler. > Do I understand you correctly that they should be compatible? > (By the way, my tdm gcc uses sjlj exceptions.) Ah yes, I believe tdm uses the MinGW.org runtime, so compatibility between my mingw-w64 based toolchains and yours would not be guaranteed. Tdm does have a GCC 4.5 release, if you want it. I would like to upload my Qt Builds, but they are very hard, if not impossible to get relocatable. Perhaps someone knows of a way better than the google code project which tried to get it right some time ago? How does Nokia make its SDK installer? > > > ... > > Ruben > > ... > > Thanks. > > > K. Frank > > ------------------------------------------------------------------------------ > WhatsUp Gold - Download Free Network Management Software > The most intuitive, comprehensive, and cost-effective network > management toolset available today. Delivers lowest initial > acquisition cost and overall TCO of any competing solution. > http://p.sf.net/sfu/whatsupgold-sd > _______________________________________________ > Mingw-w64-public mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-w64-public |