Suggestion for improvement

[John Birch]

Hi,

Isn't Project/Generate Project File what you are looking for in kdevelop1.3? 
It only makes up a project file on the complete dir - It won't add a dir to 
and existing project file. IIRC it ends up as a custom project.

jbb

On Thu, 14 Dec 2000 20:37, Werner Modenbach wrote:
> I know there are many requests for improvements and integration of this and
> that. I hesitate to throw another one on the list but I think in this case
> it is really of very general interrest.
> One thing I never understood in kdevelop is the approach to explicitely
> "import" (or specify) a new .cpp/.h file. This seems to be a little
> circumstantial (translation by leo.org ;-)) to me. Why doesn't kdevelop
> just accept all .cpp/.h files in the directory subtree?
>
> The background of my question is: I'm currently checking out CASE tools
> (i.e. Together which seems to perfectly integrate with kdevelop). One of
> the problems arising is the creation and interface definition of new
> classes. If I do that using the case tool I get files which are not part of
> the kdevelop project. I have to move them to a temporary folder and
> reimport them into kdevelop.
> I mean, I don't expect kdevelop to work together with some arbitrary tool
> but the steps described above are unnecessary.
> I have best experiences with the method of "Together" to just accept the
> files currently present in the directorytree. Dynamic generation of
> Makefile.am's and Makefiles would also make the use of CVS much more easy.
> We have real big problems in a multi developer environment to use CVS. The
> problems are mainly on makefiles and the kdevelop project file.
>
> Maybe you can give me a good reason for this approach.
>
> - Werner -
>
> BTW: I really like the great work of kdevelop!

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