[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Introducing into KDE programming
From: "=?ISO-8859-1?Q?Rafael_Fern=E1ndez_L=F3pez?=" <ereslibre () gmail ! com>
Date: 2006-09-26 22:47:24
Message-ID: 93f85fee0609261547m2e3f7890p5b65115d4047c3b () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi guys,
2006/9/26, Michael Pyne <michael.pyne@kdemail.net>:
>
> On Tuesday 26 September 2006 11:37, Rafael Fern=E1ndez L=F3pez wrote:
> > I know that a obvious response is that you may work in terminal with
> emacs
> > or something (as I do lots of times when programming), but I really lik=
e
> > KDE, so I use it for my personal window manager, file manager and so
> on...
> > despite the fact that I do use xemacs for programming.
>
> I'm the author of the kdesvn-build tool that Andras mentioned
> earlier. The
> way I have it work is I created a completely separate user to build and
> use
> KDE SVN in. If I break KDE, I can simply go back to my old user and use
> the
> system KDE just fine.
Great !! I didn't think about that...
For awhile I would even use ssh to log in to my old user to check my email,
> but as KDE SVN become more stable I eventually became a full-time user of
> my
> SVN code.
>
> > The idea of having another tree (i.e ~/kde-devel) and play with KDEDIRS
> > variable could be interesting, but I DON'T want to compile kdebase any
> time
> > that I break kdesu for example when programming or something (i know
> that
> > is not necessary, but having a unclean tree makes me crazy).
>
> You could always just run make in the build directory for kdesu.
>
> i.e.
>
> $ cd build/kdebase/kdesu
> $ make
>
> instead of
>
> $ cd build/kdebase
> $ make
>
> > For that
> > reason I thought in downloading only apps that I would like to improve
> > (i.e. kate, kmail, kdesu...) and compile them with the include dir in m=
y
> > root system and the libraries in my kde root directory.
>
> You can do this (and you can even use kdesvn-build to help) but for some
> programs (konq especially) it's more trouble than it's worth. I think it
> would work fine for kdesu though. Basically it's something like this:
>
> $ svn co -N svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdebase
> $ cd kdebase
> $ svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin
> $ svn up kdesu
>
By this method I still can't compile. I don't know what's wrong, but make
tells me that there is not a Makefile (and there is not a Makefile).
aclocal, autoconf, automake, autoreconf always tell me the same story:
"`configure.ac' or `configure.in' is required" and the only thing I can see
that is the same more or less is configure.in.in.
Sorry for this lack of time, but I've used autotools before, but not for a
vast project as KDE.
This way you'll still have the kdebase module like you should (the KDE buil=
d
> system works off of modules, not individual programs), but it will only
> contain the kdesu program.
>
> Regards,
> - Michael Pyne
Thank you,
Rafael Fern=E1ndez L=F3pez.
[Attachment #5 (text/html)]
Hi guys,<br><br>2006/9/26, Michael Pyne <<a \
href="mailto:michael.pyne@kdemail.net">michael.pyne@kdemail.net</a>>:<div><span \
class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Tuesday \
26 September 2006 11:37, Rafael Fernández López wrote:<br>> I know that a obvious \
response is that you may work in terminal with emacs<br>> or something (as I do \
lots of times when programming), but I really like <br>> KDE, so I use it for my \
personal window manager, file manager and so on...<br>> despite the fact that I do \
use xemacs for programming.<br><br>I'm the author of the kdesvn-build tool that \
Andras mentioned earlier. The <br>way I have it work is I created a \
completely separate user to build and use<br>KDE SVN in. If I break KDE, I \
can simply go back to my old user and use the<br>system KDE just \
fine.</blockquote><div><br>Great !! I didn't think about that... \
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">For awhile I would even use \
ssh to log in to my old user to check my email,<br> but as KDE SVN become more stable \
I eventually became a full-time user of my<br>SVN code.<br><br>> The idea of \
having another tree (i.e ~/kde-devel) and play with KDEDIRS<br>> variable could be \
interesting, but I DON'T want to compile kdebase any time <br>> that I break kdesu \
for example when programming or something (i know that<br>> is not necessary, but \
having a unclean tree makes me crazy).<br><br>You could always just run make in the \
build directory for kdesu. <br><br>i.e.<br><br>$ cd build/kdebase/kdesu<br>$ \
make<br><br>instead of<br><br>$ cd build/kdebase<br>$ make<br><br>> For \
that<br>> reason I thought in downloading only apps that I would like to \
improve<br>> (i.e
. kate, kmail, kdesu...) and compile them with the include dir in my<br>> root \
system and the libraries in my kde root directory.<br><br>You can do this (and you \
can even use kdesvn-build to help) but for some<br>programs (konq especially) it's \
more trouble than it's worth. I think it <br>would work fine for kdesu \
though. Basically it's something like this:<br><br>$ svn co -N \
svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdebase<br>$ cd kdebase<br>$ svn co \
svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kde-common/admin <br>$ svn up \
kdesu<br></blockquote><div><br>By this method I still can't compile. I don't know \
what's wrong, but make tells me that there is not a Makefile (and there is not a \
Makefile). aclocal, autoconf, automake, autoreconf always tell me the same story: \
"`configure.ac' or `configure.in' is required" and the only thing I can see \
that is the same more or less is <a \
href="http://configure.in.in">configure.in.in</a>.<br><br>Sorry for this lack of \
time, but I've used autotools before, but not for a vast project as \
KDE.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid \
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> This way you'll \
still have the kdebase module like you should (the KDE build<br>system works off of \
modules, not individual programs), but it will only<br>contain the kdesu \
program.<br><br>Regards,<br> - Michael Pyne</blockquote> <div><br>Thank \
you,<br>Rafael Fernández López. <br></div><br></div>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]