CVS in the make directories
tasin at e-technik.fh-muenchen.de
Fri Mar 31 10:20:32 UTC 2000
Hauke Hildebrandt wrote:
> This is probably rather a "make" than a kdevelop question:
> I somehow got the CVS directory in my project folder into the Makefile
> (it shows up under subdirs) and the compilation always stops when
> "compiling" that directory. Everything works fine after deleting it, but
> when doing "configure" again it starts all over again. How do I get rid
> of this?
Did you edit a Makefile.am/configure.in or did you get this by only
There are two files you have to look for the entry:
inside AC_OUTPUT() ... if there is a ...CVS/Makefile entry, so delete
2) Makefile.am of the parent directory to the "compiled" CVS directory:
In the assignment of variable you would find something like:
SUBDIRS = .... CVS ...
If it is outside the KDevelop specific part of the Makefile.am, so you
have added this CVS manually to it and you can simply delete the word
CVS of SUBDIRS= (or maybe the complete SUBDIRS= line if it is duplicated
inside the Makefile.am) and delete the files Makefile* of this named CVS
2. case (I guess that's yours):
If this is inside the KDevelop specific part of the Makefile.am
(means encapsulated between
####### kdevelop will overwrite this part!!! (begin)##########
####### kdevelop will overwrite this part!!! (end)############
so you have done this by adding a file to your project and as target
path you gave this CVS directory, you should remove this/these file(s)
from your project by using the right mouse button in the RFV or LFV of
You will see which file has been added by looking at the Makefile.am of
this CVS directory, there you should find an entry in xxx_SOURCES= (I
guess "xxx" would be "libCVS_a" in your case).
After having removed the wrong file(s) from your project you can delete
the files Makefile* of the "compiled" CVS directory and of course you
should commit then this working state to your local repository.
If you have done this fault for more than one CVS directory, you should
better create a new project with the same name in another project base
path and adding all source files from your old to your new project.
Maybe this would be easier and cleaner.
oohhh sveglia.... il mondo e' ammalato, ma x colpa di chi.........
:-------W. Tasin, FB 04,
<Key-Fingerprint: 1610 835F 0080 32F4 6140 6CF7 A7D0 44CD 7961A645>
More information about the KDevelop