Version: 3.0.0a7 (using KDE 3.1.1) Compiler: gcc version 3.3 20030226 (prerelease) (SuSE Linux) OS: Linux (i686) release 2.4.20-4GB After generating a New Project, with name "myapp" and type C++->KDE->Application framework, a file called "myappiface.skel" appears in the Automake Manager detail view but there is no file of that name in the "src" directory. There IS a file called "myappiface.h" in both "src" and Automake Manager, but what is it for? Is it safe to just remove these files from Automake Manager and "src"?
"myappiface.h" is a description of the DCOP interface to "myapp". This is the file you typically write yourself when you want a DCOP interface. The myappIface.h file is turned into an XML description (myappiface.kidl), which in turn is turned into C++ code (the myapp_skel.cpp file) which is the actual DCOP interface implementation but you never really need to know about. (Start 'myapp' and 'kdcop' and you'll find the myappIface interface with the openURL() method that you can call from another program - this is the purpose of the myapp_client program that is also built with this template) The DCOP interface is of course safe to remove, if you remove all references to it in the code (The myappView class inherits myappIface, for instance) See also the template README file. There is a bug here, however. As you pointed out myapp.skel is shown in the automake manager. This isn't a file at all, it is just a way to tell the KDE build system to generate the DCOP stuff. It should be filtered out from automake manager.
... or maybe not. I implemented a simple hiding of .skel files from the automake manager listing, but before committing it was pointed out to me by Ian Geiser that this would remove the functionality of removing this build system marker without editing of the makefile.am file. So.. I'm going with WONTFIX. Yes, it is confusing and there is no currenly way of _adding_ the DCOP interface marker through the automake gui, except adding a real file with the matching name (the content of which is without meaning, only the name matters). I suspect a real fix for this issue, whatever shape it takes, won't be in place before KDevelop-3.1