| 1 |
> On 06/28/2009 12:29 AM, Markos Chandras wrote: |
| 2 |
> > Another thing that changed is that we dropped the custom-cxxflags |
| 3 |
> > useflag. After a long period of testing we haven’t come across any |
| 4 |
> > problems with “advanced” cxxflags in Qt 4.5, so now we always let the Qt |
| 5 |
> > modules be built with the user- specified flags. As this is an eclass |
| 6 |
> > level change, this means also users of the stable branch will see this |
| 7 |
> > change. An emerge --newuse world will trigger a recompile of Qt, but this |
| 8 |
> > means you will get better optimizations. |
| 9 |
> |
| 10 |
> Thanks to everyone involved. |
| 11 |
> |
| 12 |
> I notice though that CXXFLAGS are duplicated. This was always that way |
| 13 |
> though, for years, but it's a bit annoying. I suppose there's nothing |
| 14 |
> that can be done about it? |
| 15 |
> |
| 16 |
> (Example, when compiling something that has to do with Qt here, the |
| 17 |
> command is: |
| 18 |
> |
| 19 |
> /usr/x86_64-pc-linux-gnu/gcc-bin/4.3.3/g++ -c -mtune=core2 -march=core2 |
| 20 |
> -O2 -fomit-frame-pointer -pipe -fno-exceptions -mtune=core2 -march=core2 |
| 21 |
> -O2 -fomit-frame-pointer -pipe |
| 22 |
> |
| 23 |
> There's no point in having everything doubled :P) |
| 24 |
|
| 25 |
Interesting |
| 26 |
|
| 27 |
Haven't noticed it |
| 28 |
|
| 29 |
This may come from |
| 30 |
|
| 31 |
sed -e "s:QMAKE_CFLAGS_RELEASE.*=.*:QMAKE_CFLAGS_RELEASE=${CFLAGS}:" \ |
| 32 |
-e "s:QMAKE_CXXFLAGS_RELEASE.*=.*:QMAKE_CXXFLAGS_RELEASE=${CXXFLAGS}:" |
| 33 |
\ |
| 34 |
|
| 35 |
or something |
| 36 |
|
| 37 |
Open a bug if you like so the rest of qt herd will be informed about this :) |
| 38 |
-- |
| 39 |
Markos Chandras (hwoarang) |
| 40 |
Gentoo Linux Developer [KDE/Qt/Sunrise/Sound] |
| 41 |
Web: http://hwoarang.silverarrow.org |
Archives