How compile Keramik?
I've downloaded the .deb for keramik but it's getting a little stale by now. How can I update to the current version? I haven't used CVS before, is there another way to get the source like there is for Mosfet's Liquid? I don't mind the CVS route if that's what's necessary, however. TIA
Re: Building Debs from KDE CVS
Ross Boylan wrote: > A recent post on kde-devel says libxml2 after 2.4.24 (as I recall) > doesn't work right. Maybe the debian version has fixed the > problem. It is fixed in libxml2_2.4.28-1 (unstable). libxml2 (2.4.28-1) unstable; urgency=low * New upstream release * Added patch from CVS to fix KDE problems. -- Hasso Tepper KDE Estonian Team
Re: Building Debs from KDE CVS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 30 November 2002 7:28 pm, Ross Boylan wrote: > A recent post on kde-devel says libxml2 after 2.4.24 (as I recall) doesn't > work right. Maybe the debian version has fixed the problem. I am sure it has - I downloaded the source of 2.4.28 and build a deb with it. Building kde still failed. I then managed to discover a later patch in the libxml2 cvs repository and was just about to patch my source and build a new deb when I noticed a new deb version (labeled as 2.4.28) had hit unstable. I installed it, and building kde then worked fine. - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96TqbuFHxcV2FFoIRAnolAJ4wdCHnR7NKD3uWBwSNHPxQdvw7AgCfWxYw dU8z5Zz/xXH+uJmvMc228xg= =j0VW -END PGP SIGNATURE-
Re: Re: Building Debs from KDE CVS
A recent post on kde-devel says libxml2 after 2.4.24 (as I recall) doesn't work right. Maybe the debian version has fixed the problem. ---Original Message--- From: Christopher Thiel <[EMAIL PROTECTED]> Sent: 11/28/02 02:21 PM To: debian-kde@lists.debian.org Subject: Re: Building Debs from KDE CVS > On Thu, Nov 28, 2002 at 07:32:24AM +, Alan Chandler wrote: > On Thursday 28 November 2002 3:51 am, Daniel Stone wrote: > > That's bizzare ... what about *latest* libxml2 from sid? > > See post above. I have had 2.4.24 for sometime and the docs have failed to > build (or take hours). There is a new libxml2 just hit unstable (2.4.28) > which seems to be slightly in advance of the source 2.4.28 in that it > contains the patch that fixes the kde docs build problem. Thank you, everything works great now! Chris Thiel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How to get Anti-aliasing to work
>Hi, > >I suggest you do the following: > >apt-get source qt-x11-free >(This downloads and uncompresses qt 3.0.5 which is recommended for KDE 3.0.5, >You need to have e.g. the following line in your /etc/apt/sources.list >deb src ftp://ftp.kde.org/pub/kde/stable/3.0.5/Debian/woody ./ ) > >Then edit the file /debian/rules in your extracted qt-x11-free-3.0.5 >directory > >Search for the text "-no-xft" and replace it with -xft Ok. I only deleted "-no-xft", but during configuration it showed xft enabled, since it seems to be the default without "-no-xft" > >Do a dch -i if you want to increase the Debian version number (to distinguish >the packages from the original ones), this is optional. dch is included in >the package devscripts. > >run dpkg-buildpackage to create the debs and install them (dpkg-buildpackage >is included in the package dpkg-dev). > >Note that it is not recommended to run XFree86 4.1.0 with xft (therefore it >was disabled). Read the RELEASE-NOTES.woody in on your kde mirror e.g. >http://ftp.du.se/pub/mirrors/kde/stable/3.0.5/Debian/woody/RELEASE-NOTES.woody > Ok. Installed XFree 4.2.0 However, even though dpkg is happy about dependencies, KDE won't start with my compiled qt3 libs. KDM crashes on startup. Why is that? >Nik > > > Hi, > > > > What version of QT does work well with debian and kde 3.0.5? Any URL about > > recompile QT to get anti-aliasing? > > Thanks, > > > > Albert > > > > Regnat Nikolaus dijo: > > > On Friday 29 November 2002 10:44, Manegold wrote: > > >> Hallo list, > > >> I use debian woody with KDE 3.04 and I can't get anti-aliasinig to > > >> work. The checkbox has no effect. When I preview a font (TT or Type1) > > >> with the Font installer in KControl-Center, the font is displayed with > > >> anti-aliasing, but not in any apps. What am I missing here? > > >> > > >> TIA > > >> Thorsten > > > > > > Hello Thorsten, > > > > > > QT is compiled without xft support. You have to recompile QT and enable > > > xft support to get anti-aliasing to work. I hope that means only the QT3 libraries, not the alll the apps as well. So I still don't have anti-aliasing. Can anyone enlighten me to why kde apps don't work with my comiled qt-libs? TIA Thorsten PS: I also tried the qt3-libs of unstable (Version 3.0.4-5), but kde (kdm) crashes with them too. Also apt-get upgrade always goes back to the compiled qt3-libs from my sources.list, even though they have the same version info as my compiled ones. Why??
Re: Build times?
On Sat, Nov 30, 2002 at 01:42:48PM +0100, Alex wrote: > I think that with a little Makefile juggling it should be possible to > half the time taken. IMHO the difference between static/shared is only > in the final linking stage. > wrong. the dynamic build is done with -fPIC, the static without. on some arches this might not matter, but on x86 it does. greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done.
Re: Build times?
On Saturday 30 November 2002 09:06, Oswald Buddenhagen wrote: > On Sat, Nov 30, 2002 at 05:06:25AM +0100, Bjoern Krombholz wrote: > > On Fri, Nov 29, 2002 at 10:53:42PM +0100, Oswald Buddenhagen wrote: > > > On Fri, Nov 29, 2002 at 05:12:49PM +0100, Bjoern Krombholz wrote: > > > > > > i'm not impressed ... the debian build does everything four times, so > > > you're not even 2.5 times as fast. :-P > > > > Hmm? I'm not shure i got it right - 4 times? Why? > > (static, dynamic) x (nothread, thread) > i didn't study the rules file in detail, but i think it needs to rebuild > the complete lib every time. ok, the factor 4 is seriously skewed by > executables (qmake, moc, designer, ...) being built only once - so > maybe it's only 3. 3.3 times as fast does not impress me, either. :) I think that with a little Makefile juggling it should be possible to half the time taken. IMHO the difference between static/shared is only in the final linking stage. Alex.
Re: Compiling KDE 3.1 on Woody
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 30 November 2002 2:29 am, Sean Fraley wrote: > I am running an install of Woody, and I would like to have KDE 3.1 on my > system. I --do not-- want to track testing/unstable to do this. There is a way round this if you have enough disk space (I am using a 4GB partition which is 72% full - including all the kde source). [You don't need to do this in a specific partition, I did so, because I am using LVM and it was easy to create this as independant unit - I in fact moved it by remounting elsewhere after I had built it.] The way do it is to choose a directory somewhere where you can create this area and use debootstrap to create a raw debian distribution in this directory. As root , you chroot to it, and then use the standard tools to build a complete debian unstable system with all the tools and libraries etc that you need to build kde. Within this chroot environment use cvs to get the latest kde sources (or any other method of getting them that you want) and then use dpkg-buildpackage -b -us -uc within each of the module directories to build the debs (its just convenient within the chrooted environment to be root -its possible to avoid but not really necessary since you are chrooted). I built qt-copy first. But you will probably need to install this before you then build arts. Then install this to build kdelibs, install these to build the rest of kde (there are some other dependencies I think - so you may have to build other modules and install them in a specific order). How to you install these debs, you may ask? Outside of the chroot environment you need to be running apache. Create a directory /var/www/debian and map it (use alias if /var/www is not your DocumentRoot) so that this was seen as url http://www.yourdoman.com/debian (where www.yourdomain.com is your local machine). Within /var/www/debian create a subdirectory /var/www/debian/kde, and as each module build finishes move the .deb files created into it. Within /var/www/debian create an override file to list all the packages (I have attached mine to this e-mail which puts all of them in a section called kde - you might want to organise them differently - in which case you will need different subdirectores). Within /var/www/debian run dpkg-scanpackages . override | gzip > Packages.gz Now now you have a repository accessible by anyone who has access to your web server. Therefore - back inside the chroot environment (and eventually outside in the main system when you are ready to install your newly build kde) add the following line to /etc/apt/sources.list (you will need change your url domain name appropriately). deb http://www.yourdomain.com/debian/ ./ Do an apt-get update and then install the packages. There are a few other things you need to be aware of. 1) You will want to build all of this with gcc-3.2 (the debian/rules files are sometimes enforcing that so you really have to go all the way). Put the following in your .bashrc file within /root of the chrooted environment. # GCC 3.2 defines export CC=gcc-3.2 export CXX=g++-3.2 export CPP=cpp-3.2 2) There seems to be a mess with automake (which is pointed at 1.4) and automake 1.5 (which is needed to build kde). I had to edit some dependencies within the debian/control file to say automake|automake1.5 (kdevelop is one that particularly comes to mind). - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE96KCPuFHxcV2FFoIRAkVGAJ9cAen3v4qU2xbTr5NDcGjsfE3DLgCZAZZm 9OiCavXB5J6yfGaO/n0iv+Y= =vHnM -END PGP SIGNATURE- amoroptionalkde ark optionalkde arts-devoptionalkde artsbuilder optionalkde artsoptionalkde cervisiaoptionalkde eyesapplet optionalkde fifteenapplet optionalkde flashkard optionalkde gideon-data optionalkde gideon-dev optionalkde gideon-doc optionalkde gideon optionalkde kaboodleoptionalkde kaddressbookoptionalkde kalarm optionalkde kalarmd optionalkde kalzium optionalkde kamera optionalkde kandy optionalkde kaphorism optionalkde kappfinder optionalkde kapptemplateoptionalkde karbon optionalkde karmoptionalkde kasteroids optionalkde kate-pluginsoptionalkde kateoptionalkde katomic optionalkde kaudiocreator optionalkde kbabel-dev optionalkde kbabel optionalkde kbackgammon optionalkde kbattleship optionalkde kblackbox optionalkde kbounce optionalkde kbugbuster opt
Re: Build times?
On Sat, Nov 30, 2002 at 05:06:25AM +0100, Bjoern Krombholz wrote: > On Fri, Nov 29, 2002 at 10:53:42PM +0100, Oswald Buddenhagen wrote: > > On Fri, Nov 29, 2002 at 05:12:49PM +0100, Bjoern Krombholz wrote: > > > i'm not impressed ... the debian build does everything four times, so > > you're not even 2.5 times as fast. :-P > > Hmm? I'm not shure i got it right - 4 times? Why? > (static, dynamic) x (nothread, thread) i didn't study the rules file in detail, but i think it needs to rebuild the complete lib every time. ok, the factor 4 is seriously skewed by executables (qmake, moc, designer, ...) being built only once - so maybe it's only 3. 3.3 times as fast does not impress me, either. :) > > > Compiling C++ stuff takes much longer than plain C because of the > > > preprocessing > > cpp does not not need much time, > > Never said anything else. ;) > of course. :) > > a) g++ is slower than gcc > > Aren't those both the same, more or less? > (`g++' equals `gcc -lstdc++ -lm') > look behind the curtain. ;) hint: /usr/lib/gcc-lib/ greetings -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done.
