Re: Athlon optimized KDE build
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I assume that is from CVS HEAD.
I'd used, more or less, the following script. Everything there is needed.
export PATH=/usr/local/kde3/bin:$PATH
export CFLAGS="-O3 -march=k6 "
export CXXFLAGS="-O3 -march=k6 "
make -f Makefile.cvs
#rm -rf kde3
mkdir kde3
cd kde3
../configure --enable-debug --prefix=/usr/local/kde3 \
- --with-qt-dir=/usr/local/qt --disable-fast-perl \
- --disable-rpath --disable-path-check
make
This will do for you.
If you want to optimize more I suggest you to use --enable-final
- --disable-debug --enable-fast-malloc=full in configure flags (of course
removing --enable-debug), and indicate your submodel properly (i686, etc.)
in the compiler flags. Another safe one is -malign-functions=4 which will
speed up code fetch. Less safer are flags like -fstrict-aliasing
- -fomit-frame-pointer.... Feel free to experiment with remaining optimization
flags (that are not induced by -O3). :)
For qt, I used the following configuration...
# assuming you are running this in qt-copy
export QTDIR=`pwd`
echo $QTDIR
export YACC='bison -d'
#make -f Makefile.cvs
./configure -system-zlib -qt-gif -system-libpng -system-libjpeg \
- -plugin-imgfmt-mng -thread -no-stl -no-xinerama -no-g++-exceptions \
- -platform linux-g++-k6
linux-g++-k6 is simply linux-g++ copied over with the following flags added:
orion:kde$ grep QMAKE_CFLAGS_RELEASE qt-copy/mkspecs/linux-g++-k6/qmake.conf
QMAKE_CFLAGS_RELEASE = -O3 -march=k6
QMAKE_CXXFLAGS_RELEASE = $$QMAKE_CFLAGS_RELEASE
Anybody knows a better way to tell Qt to use your own set of flags? I think
I'd tried usual ways, but qmake hadn't seemed to comply.
Sincerely,
- --
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara
www: http://www.cs.bilkent.edu.tr/~erayo
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8fnFlfAeuFodNU5wRAnlpAJwLUxZDPXSxxxQbxHFmAg5ZhqEfMwCfU1Oj
RlU0rdzovjD3Ts4bsv2yHQ4=
=+8hm
-----END PGP SIGNATURE-----
Reply to: