🔒 Locked

Directory structure for development

Started by terenctb Sep 8, 2006 at 4:42 AM 2 replies 600+ views

Original Post

Sep 8, 2006 at 4:42 AM

Friday! I was just wondering about opinions on directory organization structure of your projects for the most part I stick to a pretty *nix one. root | |-<doc> |-<project> - used for all assets, and/or current working directory |-<build> - used for building builds via a bat file or script file |-<lib> |-<bin> - utils and the like |-<prj> - project files and the like |-<source> - source *|-<include> - I hate this..thinking of dropping it. *|-<modulea> etc

CadetUmfer

Sep 8, 2006 at 1:00 PM

Something like this. Not the best, but gets the job done.

/$(ProjectName) {source files}
/$(ProjectName/obj {object files}
/bin/$(ConfigurationName)/$(ProjectName) {executables/dlls}
/lib/$(ConfigurationName/$(ProjectName) {libs}
/dependencies/lib/$(ConfigurationName)
/dependencies/include
/shared [headers shared between projects
/final/$(ConfigurationName) {final build, all .exe and .dll get xcopied here}
/final/media
/final/script

TheShawnPeter

Sep 8, 2006 at 2:02 PM

For OOP I always have a folder called sCrap. It's where all of trials & failed attempts end up for reference. Not sure if I intend it to mean scrap or shawn's crap.

ApochPiQ

1,378

ApochPiQ

Sep 8, 2006 at 2:39 PM

Nice and boring:

d:/projectname/code d:/projectname/build d:/projectname/docs d:/projectname/tools

Actual contents of each section varies an awful lot by project; usually it's fairly arbitrary.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.