Hi! Could anyone give me some good advice in setting up a source tree that will be controlled by CVS? I read that one of the weaknesses of CVS is dealing with moved directories / files, so I'd hope someone can give me some clues here...
Alright, here we go. This is what I can foresee now at the start: - "engine code" will be mainly ANSI C++ source code (so: headers and implementation files) - for the user interface, Java code will most probably be used - multiple projects / applications need to be built from the same sources both on Windows and Linux: . on Linux, GNU suite is used (CodeWarrior IDE is also an option, any good?) . on Windows, MSVC++ is used - a few external C++ libraries will be needed (matrix operations, neural networks, DSP any advice?); some might have the source code available, others might have just a library with header - documentation for our own sources is extracted from the source files using Doxygen (HTML and hyperlinked PDF) I was thinking about the following tree structure (I highly appreciate any remarks/thoughts/suggestions you might have): *** in short *** project\ project\applications project\applications\common project\applications\linux project\applications\win32 project\codebase project\codebase\common project\codebase\linux project\codebase\win32 project\docs project\external *** in detail *** project\ main root for the project's files project\applications main root for the applications that will be built from the codebase and the external sources/libraries project\applications\common common project settings/build configurations/resources for the applications project\applications\linux project settings/build configurations/resources for the linux applications project\applications\win32 project settings/build configurations/resources for the win32 applications project\codebase main root for our own source code project\codebase\common common source code (both headers and implementation files) need to split in Java and C++ ? project\codebase\linux Linux specific source code (both headers and implementation files) (most things can be kept common by using #ifdef OS statements) project\codebase\win32 Linux specific source code (both headers and implementation files) project\docs Doxygen settings and extra files for generating the documentation project\external subdirectories contain downloadable packages from third parties (might include source trees or library/header sets) All kind of advice welcome! Koen _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
