We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I find that having a "standard" project directory with sub-directories for all projects to be of great value.
I do not know what others have done when they start a new project, but I can tell you that I simply copy-n-paste, then rename this "template" into my ..\Projects\ directory, and then work from within the template's standardized structure.
e.g. ..\Projects\Alpha
Where "Alfa" is the renamed standardized structure.
I will add sub-directories to this standard structure when it is deemed appropriate. I highly recommend this structure to people who work on multiple projects and add this bit of advice to their methods.
--Cpt. Vince Foster 2nd Cannon Place Fort Marcy Park, VA
In that case, they would go in "common". what about what is common for build3, build 11, build14 ... but not all builds
However, if you really have 47 variants, then you really should be using a proper configuration management tool. which I do (a very elaborate .bat file that does it all)
Erik
"common" would be anything shared by more than one build - so "shared" might be a better name.
Or, as I said, you could also have other "groups"
project project\common -- Sources common to ALL builds project\feature-a -- Sources common to builds with Feature 'A' project\feature-b -- Sources common to builds with Feature 'B' project\feature-c -- Sources common to builds with Feature 'C' project\variant1\src -- Sources unique to Variant 1 project\variant1\obj -- All objects from building Variant 1 project\variant1\lst -- All objects from listings Variant 1 project\variant1\src -- Sources unique to Variant 1 project\variant1\obj -- All objects from building Variant 2 project\variant1\lst -- All objects from listings Variant 2
Andy, how would you the above with ONE 'project file' not 47 to maintain? I only have one .bat for building all 47 versions
in the top, 'project', folder.