Copy project directory

Robert robertLinux at gmx.de
Fri Jun 20 03:04:24 BST 2003


Hello.
Am Freitag, 20.06.03 um 00:10 Uhr schrieb Matthias Bach:

> I don't really see your problem. Just go the the commandline and enter:
> cp myProject myProjectCopy

Yes, but that gives me a directory with all that files I didn't have 
when creating the project. (Makefiles, config etc.). Maybe it is better 
to have a clean dir??

Additionally, creating my project (it is a very small one for 
evaluating different IDE's) gave me the following directory structure:

countedbodytest/countedbodytest

with all sort of stuff I didn't write in countedbodytest/ and my 
sources in countedbodytest/countedbodytest/

Now I cp with a new name I get
countedbodytest_copy/countedbodytest

Is it safe to have a dir structure that way? It could become (later) a 
very big project with lots of sources and headers.

Now I create a subdir called test and a file test.cpp.

I just see, that it is not possible to group files in distinct 
directories? Well, yes it is possible in Project->Add existing 
File(s)... with the proper pathToSourcefile==pathToDestinationfile 
setting. Funny. I opened test.cpp that way

but then I cannot group my file in the IDE in the Groups view? Every 
.cpp is clashed into Sources, regardless from its origin?

Shouldn't that be a subdir called test nested into Sources? Shure, I 
can create that manually; I did, called it Test, but I cannot add (or 
move) test.cpp there. The rule in Sources properties seem to catch my 
test.cpp before it can be catched by Test. Weird.

Are my assumptions right or can you delighten me further? I wan't to 
find an IDE for large projects and its absolutely important to group my 
files not by suffix but by subject.

Thank you for your valuable time,
Robert


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



More information about the KDevelop mailing list