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

List:       kde-devel
Subject:    Re: Newbie Guide to Building KDE from CVS. Comments sought.
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2003-09-15 22:46:10
[Download RAW message or body]

On Tuesday 16 September 2003 00:06, Gary Cramblitt wrote:
> On Fri, 12 Sep 2003 00:27:38 +0000
>
> "Mahfouf Anne-Marie" <annemahfouf@hotmail.com> wrote:
> > Hi,
> >
> > I have an article basically doing the same
> > http://women.kde.org/articles/tutorials/howtocvs.php
> > but the more the better :-)
>
> Something in the KDE tips section on the website I wonder about.  On the
> page at
>
>   http://women.kde.org/tips/kdetips.php
>
> it says
>
> <quote>
> When compiling KDE applications furthermore the following environment
> variables should be set: MANPATH=$KDEDIR/man:$QTDIR/man:$MANPATH
> LD_LIBRARY_PATH=$KDEDIR/lib:$QTDIR/lib:$LD_LIBRARY_PATH
> LIBRARY_PATH=$LD_LIBRARY_PATH
> CPLUS_INCLUDE_PATH=$KDEDIR/include:$QTDIR/include:$CPLUS_INCLUDE_PATH
> export MANPATH LD_LIBRARY_PATH LIBRARY_PATH
> export CPLUS_INCLUDE_PATH
> </quote>

CPLUS_INCLUDE_PATH: i do not know what it is. It seems to be where to find the 
includes.

MANPATH: path to the man pages. KDE has no man pages Well, Debian have some 
for KDE, they are in KDE's source but are not build and installed by KDE. 
Someone had wish that this should change and that Debian's man pages become 
the official KDE ones but as far as I know nothing was made.

LIBRARY_PATH: it helps ld.so (the run-time linker) to find its library. The 
problem is that this environment variable is considered by some as a security 
risk and therefore disabled. However when available, this environment 
variable permits to have 2 KDE versions with one user name (which is not the 
case in your tutorial.)

>
> The MANPATH variable is also covered in the article you wrote.  I
> didn't mention the MANPATH, LIBRARY_PATH, and CPLUS_INCLUDE_PATH
> variables in my article.  They don't seem to be necessary on my system
> (RedHat 9).  I haven't seen them mentioned in other articles either.
> Should I add these to my article or not?

If it works without, I think that you should better leave them. (The newbie 
has already enough environment variables to "wonder" about.)

>
> Also, in your article, you have
>
> <quote>
> Note for Suse users: in /home/kde3/.xinitrc, replace the line
> exec $WINDOWMANAGER
> by
> /usr/local/kde3/bin/startkde
> </quote>
>
> Should I add this to my article?  Since "/usr/local/kde3/bin" is

No! Defining $WINDOWMANAGER is enough!
export WINDOWMANAGER=/usr/local/kde3/bin/startkde
does the same without changing X-Window and without disabling other window 
manager (including the old KDE.)

> in the PATH, wouldn't just "startkde" be better?
If you are sure that your new startkde is in the $PATH before the old one, 
then you do not need it.

However it avoids to start the old KDE when the new startkde is missing due to 
a bad install.

>
> Regards,
> Gary

Have a nice day!

>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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