Userdefined directories in K-develop

[Christer Sandberg]

tisdagen den 16 april 2002 16:29 wrote Dirk Broer:
> I'm not exactly sure of your exact predicament.
>
> I'm working on a project where they have:
> ./html
> ./src
>
> with the make file only in the ./src directory.
>
> I pointed Kdevelop at ./ and selected "generate project files" and kdevelop
> when through the tree and found all the files and recognized that it was
> under CVS control.
Well, I have tried that one too. Kdevelop then creates a project containing 
all the sources, but no makefiles, if I select "Configure" (without arguments 
since I have no clue what arguments to feed it with) or "Autoconf ..." from 
the Build menu I get "/bin/sh: ./configure: No such file or directory" and 
"gmake: Makefile.cvs: No such file or directory
gmake: *** No rule to make target `Makefile.cvs'.  Stop." respectivley.
As for you kdevelop has detected the existence of CVS and check that in the 
project options. 
Since it fails to generate makefiles it is definitely not able to build 
sources.
BTW when starting to generate the project it warned for missing makefile.am.
I don't know how to write .am files, but kdevelop is quite keen on creating 
them if I instead start with Project/New instead of Project/Generate. But 
Project/New insted gives me the problems I mentioned in the previous mail, 
i.e. it gives me a directory tree that I can't use because it doesn't map 
that of the existing CVS...
Thanks anyway Dirk.

A bit strange because my case seems to be quite normal, and K-develop seems 
to be quite well done capable of lots of things, why not a "quite normal 
project"?

Any other suggestions?

Christer 


>
> To get the build to work, I created a Makefile in the top directory that
> was:
>
> ${MAKECMDGOALS}:
> 	${MAKE} -C src $(MAKECMDGOALS)
>
> That seemed to be enough.
> From kdevelop, simply select Make and it does a Make all
> I believe I added 'all' to the build options.
>
> I can't use the debugger easily since the src directory is used to generate
> about 30 different executables.  Everything else seems to work though.
>
> Dirk
>
> On Tuesday 16 April 2002 08:59 am, you wrote:
> > I have just joined a C++ development project. The project already uses
> > CVS for version handling. The problem is that the directory tree in CVS
> > does not match the structure prefered by K-develop (it is
> > projowner/CVSROOT/projname/src/xxx where xxx is the different source
> > directories, there are no source files directly in the src directory).
> >
> > Obviously there is no way to get CVS in K-develop work with this in
> > combination with proper generation of makefiles - I have given up that
> > idea. Actually it is nearly as good using a terminal for the CVS.
> >
> > However I would highly appreciate to be able to use the build tools in
> > K-devlop, and in particular the integrated debugging facility, and this
> > without too much effort on editing makefiles ( I am supposed to produce
> > things pretty soon and I have already burned some working days on Linux,
> > to which I am a newbe). I have read about makefiles, and understand the
> > basic ideas with dependecies, but I am lost when trying to read the ones
> > generated by config.
> >
> > So my question is how get K-develop to do as much as possible keeping our
> > original directory tree. If I have to create all my makefiles manually
> > (or some of them), what must they contain to bring K-develop to
> > understand them when I select "build/make"?
> >
> > Worth to mention: the project members work on different platforms.
> >
> > Any ideas are welcome!
> > Christer
> >
> > -
> > to unsubscribe from this list send an email to
> > kdevelop-request at kdevelop.org with the following body: unsubscribe
> > »your-email-address«
>
> -
> to unsubscribe from this list send an email to
> kdevelop-request at kdevelop.org with the following body: unsubscribe
> »your-email-address«

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«