[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: KDE2 build instructions
From:       Emily Ezust <gexcfxyy () umail ! corel ! com>
Date:       2000-04-03 15:02:31
[Download RAW message or body]

Below is the text of the attachment that Ming sent, for those of you who 
are allergic to HTML.

Please note: I wrote it several months ago and would like to add a
correction: Don't have "$KDE_CODE_DIR/kdebase/startkde" in your .xinitrc 
but rather "$KDEDIR/bin/startkde". (Sorry! - that was my first
draft. :-)

-Emily

Ming Poon wrote:
> 
> The stuff below is a couple of months old. I hope it helps. Let us if
> there is any error or stuff that should be added . We are trying to do
> more KDE howto too for everyone to use. (Just ignore the Corel LINUX
> part if you are not using Corel LINUX). Thanks.
> 
> ----------------------------------------------------------------------
> 
> Installing KDE2
> Some notes compiled by Emily Ezust <emilye@corel.com>
> [This is from memory - please let me know if I'm missing anything!]
> 
> 1. Install Corel Linux on a fresh machine to get the system all set up
> 
> easily
> 
> 2. Purge the kde-corel and qt-corel packages
> 
> 3. Make sure you have autoconf 2.13-11, automake 1.4-2 and byacc
> 1.9-11.6
>    or later.
> 
>    You can obtain these by anonymous ftp from my machine:
>       ftp://120.169.1.110/pub/
> 
>    Put KDEDIR=/usr/X11R6 in your environment.
> 
> 3. Use cvsup to grab the latest KDE2 source code
>    (see http://www.kde.org/cvsup.html for instructions)
> 
>    Note: you really only need qt-copy, kdesupport, kdelibs and kdebase
> 
>    to start out with. Add other modules as necessary.
>    The qt-copy module is the most recent snapshot of Qt2 that
>    KDE requires. It is updated whenever someone needs a new feature
>    in Qt (iff the snapshot compiles!).
> 
>    I've been putting my KDE source code in
> KDE_CODE_DIR=/home/emilye/kde
>    but where you put it is up to you.
> 
>    The code often does not compile - check kde.kde.devel to see if
> anyone
>    has noticed yet - it's ok to report it there.
> 
>    If you can't connect with cvsup, try a mirror or wait a little
> while.
>    With real CVS access (granted by Stephan Kulow on polite request,
>    coolo@kde.org), you can almost always connect.
> 
> 4. The order of compiling and installation that works most reliably
> is:
>    qt-copy
>    kdesupport
>    kdelibs
>    kdebase
> 
>    Do all the steps of compilation and installation before moving
> to the next module:
>     ln -s ../kde-common/admin .
>     make -f Makefile.cvs
>     ./configure
>     make
>     make install
> 
>   Note: once you have access to the real CVS and can do
>     $ cvs up
>   you won't have to do the first step.
> 
> 5. Put "$KDE_CODE_DIR/kdebase/startkde" to your .xinitrc.
>    Then run startx.
>    Enjoy.
> 
> 6. Once you have real CVS access, you might want to put this in your
>    .cvsrc:
>       update -dP
>       diff -u
>       cvs -qz6
>       checkout -P
> 
> Misc. Notes:
>   You may have to give the startkde file execute permission. Last time
> I
> checked, it was not given this automatically.
>   If you get a compilation error in kdebase/kcontrol having to do with
> 
> libbgnd.la, it might be a makefile dependency problem. This might do
> the
> trick: cd kdesktop; make; cd ..; make
>   kpanel is now kicker. kfm is now konqueror. kdelibs is very
> different from
> KDE1-1 kdelibs. Many APIs have been completely redone.
>   Read the Developer's How To:
> 
> http://developer.kde.org/documentation/tutorials/howto/develHOWTO.html
> 
>   http://developer.kde.org/ is your friend.
>   Read the kde* groups.
>   Beware: make clean doesn't always work. Sometimes you have to also
> do:
>        rm -r .deps/
>        rm *.moc*
> 
> Federico David Sacerdoti wrote:
> 
> > Hi,
> >
> > Could someone point me to some general KDE2 build instructions. I
> > have the CVS
> > tree mirrored with cvsup and just need some guidance on how to
> > compile
> > KDE from scratch - which modules to make first, things to watch out
> > for, etc.
> >
> > Thanks,
> > Dave
> >
> >  --
> > Federico David Sacerdoti
> > S Linux Machines
> > www.slinuxmachines.com
> 
> --
> Do you know about Corel's involvement with Linux?  Visit us at
> http://linux.corel.com
> 

-- 
Emily Ezust, emilye@corel.com
Corel Corporation
(613)728-0826, x 5936
-- 
The address in the headers is not the poster's real email address.  Do not send
private mail to the poster using your mailer's "reply" feature.  CC's of mail 
to mailing lists are OK.  Problem reports to "postmaster@umail.corel.com".  
The poster's email address is "emilye@corel.com".

[prev in list] [next in list] [prev in thread] [next in thread]