gigafalk at yahoo.com
Mon Dec 11 06:36:26 UTC 2000
Ivan Hawkes wrote:
> but the ./configure doesn't create files in
> my new subdirectory - not sure why.
You must add your new directories to $KDEVELOPDIR/configure.in.in. That file is processed when generating the
temporary project files.
This should remove a bunch of errors...
> Do I have to do a make install each time to test my work?
The dynamic libraries are taken from $KDE2DIR/lib. That's why make install accordingly with changes there.
> This seems odd. Is
> there a way to set the project up so it executes the latest compiled version
> of my code, rather than me having to make install all the time?
the binary (kdevelop) itself can be started from KDevelop itself by clicking "Execute" or "Debug". It will
start the local version, not the one in $KDE2DIR/bin, you know.
> Plenty of dumb questions there...
There are no dumb questions. :-)
> but I'm still coming to grips with all this
> stuff, and there's a large codebase with very little docs.
As usual, all explains itself. ;)
No, a short manual for programming KDevelop-parts should be nice.
F at lk
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
More information about the KDevelop-devel