KDevelop 3 and KDE CVS Repository
Alexander Dymo
cloudtemple at mksat.net
Sun Nov 16 19:01:19 GMT 2003
On Friday 14 November 2003 01:37, you wrote:
> 2. Deleted a whole bunch of files, and added their names to
> .cvsignore files. I ended up with the following:
Hmm, alas this should be really done manually. I know no good way to do
this cleanup automatically.
> 5. Did "cvs up" to make sure my working directory matched the repository.
<skip>
> 6. Went to /kdenonbeta and created a file called inst-apps with "applets"
> in it. Then did "make -f Makefile.cvs" and "./configure". Configure
> errored out with "invalid directory". I traced the problem to the
> kclipspellapplet/Makefile.am that KDevelop created. Here it is:
<skip>
> --------------
> SUBDIRS = $(TOPSUBDIRS)
> Configure was erroring on the first part of this file, attempting to
> "cd" to applets directory.
You can replace $(TOPSUBDIRS) by a list of directories like
SUBDIRS = foo1 foo2 foo3
to avoid problems with subdrs without makefiles.
>Even had that worked, I can see that this
> Makefile.am won't possibly work because it relies on the admin directory
> and KDE CVS repository will not permit you to add an admin directory.
But it permit you to checkout this directory like
cvs co kde-common/admin
If you take a look at, for example, kdevelop or kdelibs or kdebase cvs
repository, you will find that admin directory is there anyway.
I believe it is symlinked on cvs server (but I may be wrong).
> 7. I concluded that KDevelop's build system and the KDE CVS build
> systems are incompatible. So I replaced /kclipspellapplet/Makefile.am
> with this:
>
> ---------------
> SUBDIRS = src
> ---------------
You can do it, but it's better to leave things as is (only replacing
$TOPSUBDIRS with src).
> I also had to add "kclipspellapplet" to the SUBDIRS line in
> /kdenonbeta/applets/Makefile.am. This seems to work, I think. But I
> cannot run KDevelop directly against my
> /kdenonbeta/applets/kclipspellapplet directory.
In the worst case you can checkout your module from cvs and import it
as an automake project in KDevelop.
> How are other people doing this?
Look at KDevelop source tree in cvs. We use KDevelop for developing on
the local KDevelop copy from repository.
--
Alexander Dymo
Ukrainian State Maritime Technical University, IT Department
-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«
More information about the KDevelop
mailing list