[Bug 69623] kdevelop project file sync option missing

Janne Karhunen janne.karhunen at pp.htv.fi
Thu Dec 4 14:26:03 UTC 2003


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=69623     




------- Additional Comments From janne.karhunen at pp.htv.fi  2003-12-04 14:24 -------
No, project top level Makefile (or any other file named Makefile for that matter) doesn't include any sources. Makefiles are generated, just like in autotools case, except that it's a proprietary tool that generates those. It even does this 'on the fly' (just adding a file into a directory is enough for it to start compiling a file). Top level Makefile exists only for KDevelop et al to give us those 'well known targets' (all, clean..) and build buttons. Makefile really consists of only a series of commands to compile the project.

Besides, even if this wouldn't be the case, how could kdevelop interpret all possible ways of writing a Makefile (meaning how could it detect all project files from them)? Sure, adding a file to a standard Makefile makes it usually to compile, but this was all about KDevelop being able to detect that and to stay in sync. For me, occasionally manually triggering source file 'finds' in a directory tree or triggering it after performing an action such as 'cvs up' seems like an only way.




More information about the KDevelop-devel mailing list