kdevelop error: no rule to make target.. is it a bug?
 

I have Kdevelop 3.1.2.
I am developing a C++ application. In that, when I try to add a subprojoject and compile, it ends up in giving a message like

gmake[1]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug/src'
Making all in grid
/bin/sh: line 0: cd: grid: No such file or directory
gmake[2]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug/src'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Target `all' not remade because of errors.
gmake[1]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug/src'
gmake: *** [all-recursive] Error 1
gmake: Target `all' not remade because of errors.
gmake[1]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug'
gmake[1]: Nothing to be done for `all-am'.
gmake[1]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug'

in the above, the subproject name is grid. And the project name is ggrid.

If i create a directory called grid, i get this error

cd '/home/tslssd/coding/GUI/ggrid/debug' && WANT_AUTOCONF_2_5="1" WANT_AUTOMAKE_1_9="1" gmake -k -j1
Making all in src
gmake[1]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug/src'
Making all in grid
gmake[2]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug/src/grid'
gmake[2]: *** No rule to make target `all'.
gmake[2]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug/src/grid'
gmake[2]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug/src'
gmake[2]: Nothing to be done for `all-am'.
gmake[2]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Target `all' not remade because of errors.
gmake[1]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug/src'
gmake: *** [all-recursive] Error 1
gmake: Target `all' not remade because of errors.
gmake[1]: Entering directory `/home/tslssd/coding/GUI/ggrid/debug'
gmake[1]: Nothing to be done for `all-am'.
gmake[1]: Leaving directory `/home/tslssd/coding/GUI/ggrid/debug'
*** Exited with status: 2 ***

but, a similar project (i duno when i created it) compiles well with same kdevelop. Duno where the thing is screwed up now...

Can anyone help me with this?

after half day of juggling with it, i came up with the following remedy....

use automake 1.7

and, when u used kdevelop and create subproject, check the configure.in at the last line in AC_OUTPUT if the subproject directory is included as below

AC_OUTPUT(Makefile src/Makefile grid/Makefile bspline/Makefile)

in the above line, grid and bspline are subprojects. then run

% automake grid/Makefile
% automake bspline/Makefile
% autoconf

./configure

make

whola.... its working, and i can use kdevelop again...

hope it helps some one like me.... :)

cheers,
LintoWinWin

Thank you!
 

Hi LinToWinWin,

Thank you!

This was a great help for my mental health!!

BR,
Max.

kdevelop - 3.5.1 (ubuntu 8.04) project setup just drives me crazy
 

It is bizzar. I've made several projects with kdevelop before and actually really like to work with it. It is a nice tool, once you figure out how to teach it what it's supposed to do when you press the F8 key (build project). Before that it can be hell.
Kdevalop's wizardry seems to run in catch 22 cycles when I try to either make a new project, or import an existing project, or even if I try to just start from a little main program that uses 2 or 3 header files containing C++ class definitions that I had used before in other projects.

Here is my problem at the moment: I had a working project in which I had defined a few C++ classes. Now I wanted to take only a few of these, and start over with an entirely new project. I tried all kinds of things without success.

I open up "new project from the menu and choose C++ automake project. It creates a whole bunch of files in the specified directory and then immediately complains that there wasn't an active target specified. (Not my fault! I say.) There is no obvious way how to specify a target, if I haven't even a line of code in the project at that point. Yet, kdevelop wants a target. When I try to add a new class it says: If you don't have a target, I will create new files when you define a new C++ class but won't include them in the project. So what is a target? And how am I supposed to create one? I tried all kinds of methods to add the existing files, but always seem to miss some point, resulting in a situation where something is missing that should be there (all the different .in and .am files are completely opaque to me, and the error messages mean nothing).

I tried also the other way around: I have a two .h files and two .cpp files containing class definitions, and one main.cpp in a directory, then tried to create a new project: It can't do it since the directory corresponding to the project already exists - stuck again. Finally, I tried to specify that I want to import the existing files. It imports them, shows the classes in the class trees, but then never gets to create any make files, complaining that there aren't any configure files, and automake, if run from the console complains also that it's missing input files to do anything.

I'm sorry this got such a long rant, I feel a bit at the end of the rope: It is because I can't figure out anymore how I ever managed to create other kdevelop projects before successfully. Was there anything added in terms of wizardry that is now suddenly in the way? My guts feeling is that this confusion with kdevelop is a common experience. (Some one please tell me that I'm not completely insane :-)

This is Kdevelop 3.5.1 on Ubuntu 8.04

Got any pointers? Thank you