Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualShyGuy92

Posted 05 August 2013 - 09:35 AM

Hello Guys,
 
I am an experienced C++ programmer and have been using several project structures, like simple src and obj folders and using the command line, default structures provided by IDEs such as the Code::Blocks, etc. With my experience the complexity of my projects grow and again I am thinking of an efficient directory structure for my projects... of course I have already searched the internet, but I didn't find any examples perfectly fitting my needs... so I think, I show you my beta structure to gather opinions, modification and improvment suggestions.

My structure is of course meant to be used for developing platform independent games (mostly basing on SDL, SFML etc.). In addition, most of my projects would also need tools (either command lines, or GUI using Qt) for level editing, file converting etc. Here is my current structure (EDITED):
 
    bin/
    └ [the executable file (Windows, Linux, ...) including DLLs (Windows)]
    share/
    └ [project-title]/
      └ [all program data, like graphics, level files, etc.]
    src/
    └ [program or tool name]/ [for project specific libraries: lib*]
      └ forms/
        │ └ *.ui [QtDesigner files => ../../../build/[program-name]/ui/ui_*.h]
        ├ *.cpp [=> ../../build/[program-name]/deps/[debug/release]/*.d; ../../build/[program-name]/obj/[debug/release]/*.o]
        ├ *.h
        └ *.rc [Windows Resource script for version information => ../../build/[program-name]/obj/[debug/release]/*.o]
    lib/
    └ lib*.a, lib*-d.a [second one for debugging]
    include/ [project specific libraries' includes]
    └ [library name]/
      └ *.h
    resource/ [Icons, ... for the tools; for the generation of the .rcc file]
    ├ appicon/ [application icon, e.g. for the desktop or window icon]
    │ └ *.png, *.ico [second one for Windows Resource file]
    ├ icons/ [UI icons, e.g. "open" or "paste" icon]
    └ *.qrc [an XML file listing all files for the .rcc output file => ../share/[project-title]/tools/*.rcc]
    doc/ [source documentation generated by doxygen]
    build/
    └ [program or tool name]/
      ├ obj/
      │ └ [debug / release]/
      │   └ *.o
      ├ deps/ [might have debug and release subdirs as well]
      │ └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
      ├ ui/
      │ └ ui_*.h [translated .ui files for including in the source code]
      └ moc/
        └ [debug/release]/
          └ moc_*.cpp [Qt MetaObject files => ../../obj/[debug/release]/moc_*.o]
    tags/
    dist/ [distributable files]
    ├ source/
    ├ windows/
    │ ├ inno-installer/ [or nsis-installer, etc.]
    │ │ ├ [installer script, not distributed]
    │ │ └ [generated .exe file for distribution]
    │ └ [portable archive file]
    └ linux/

Notes:
 - the windres tool (MinGW) can generate a .o file from a .rc file
 - the debug executable might have a suffix, such as -d or -debug (tool-name-debug.exe)
The end user shall receive the bin and share folders.
Maybe the structure is more than good enough and some of you might find it useful for himself.
I ask for feedback smile.png

#4ShyGuy92

Posted 02 August 2013 - 02:52 AM

Hello Guys,
 
I am an experienced C++ programmer and have been using several project structures, like simple src and obj folders and using the command line, default structures provided by IDEs such as the Code::Blocks, etc. With my experience the complexity of my projects grow and again I am thinking of an efficient directory structure for my projects... of course I have already searched the internet, but I didn't find any examples perfectly fitting my needs... so I think, I show you my beta structure to gather opinions, modification and improvment suggestions.

My structure is of course meant to be used for developing platform independent games (mostly basing on SDL, SFML etc.). In addition, most of my projects would also need tools (either command lines, or GUI using Qt) for level editing, file converting etc. Here is my current structure:
 
    bin/
    └ [the executable file (Windows, Linux, ...) including DLLs (Windows)]
    share/
    └ [project-title]/
      └ [all program data, like graphics, level files, etc.]
    src/
    ├ *.cpp [=> ../build/deps/[debug/release]/*.d; ../build/obj/[debug/release]/*.o]
    ├ *.h
    └ *.rc [Windows Resource script for version information => ../build/windows/[debug/releasse]/*.res]
    doc/ [source documentation generated by doxygen]
    build/
    ├ obj/
    │ └ [debug/release]/
    │   └ *.o
    ├ deps/
    │ └ [debug/release]/
    │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
    └ windows/
      └ [debug/release]/
        └ *.res [Windows Resource file]
    tools/
    ├ bin/
    │ └ [the executable files/tools (Windows, Linux, ...) including DLLs (Windows)]
    ├ share/
    │ └ [project-title]/
    │   └ tools/
    │     └ *.rcc [Qt resource file for tools, contains icons for example]
    ├ resource/ [Icons, ... for the tools; for the generation of the .rcc file]
    │ ├ icons/
    │ └ *.qrc [an XML file listing all files for the .rcc output file => ../share/[project-title]/tools/*.rcc]
    ├ src/
    │ └ [tool-name]/
    │   ├ forms/
    │   │ └ *.ui [QtDesigner files => ../../../build/[tool-name]/ui/ui_*.h]
    │   ├ *.cpp [=> ../../build/[tool-name]/deps/[debug/release]/*.d; ../../build/[tool-name]/obj/[debug/release]/*.o]
    │   ├ *.h
    │   └ *.rc [Windows Resource script for version information => ../../build/[tool-name]/windows/[debug/release]/*.res]
    ├ doc/ [source documentation generated by doxygen]
    │ └ [tool-name]/
    └ build/
      └ [tool-name]/
        ├ obj/
        │ └ [debug/release]/
        │   ├ *.o
        │   └ moc_*.o [translated Qt MetaObject files]
        ├ ui/
        │ └ ui_*.h [translated .ui files for including in the source code]
        ├ moc/
        │ └ [debug/release]/
        │   └ moc_*.cpp [Qt MetaObject files => ../../obj/[debug/release]/moc_*.o]
        ├ deps/
        │ └ [debug/release]/
        │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
        └ windows/
          └ [debug/release]/
            └ *.res [Windows Resource file]
The end user shall receive the bin and share folders.
Maybe the structure is more than good enough and some of you might find it useful for himself.
I ask for feedback smile.png

#3ShyGuy92

Posted 01 August 2013 - 04:24 PM

Hello Guys,
 
I am an experienced C++ programmer and have been using several project structure, like simple src and obj folders and using the command line, default structures provided by IDEs such as the Code::Blocks, etc. With my experience the complexity of my projects grow and again I am thinking of an efficient directory structure for my projects... of course I have already searched the internet, but I didn't find any examples perfectly fitting my needs... so I think, I show you my beta structure to gather opinions, modification and improvment suggestions.

My structure is of course meant to be used for developing platform independent games (mostly basing on SDL, SFML etc.). In addition, most of my projects would also need tools (either command lines, or GUI using Qt) for level editing, file converting etc. Here is my current structure:
 
    bin/
    └ [the executable file (Windows, Linux, ...) including DLLs (Windows)]
    share/
    └ [project-title]/
      └ [all program data, like graphics, level files, etc.]
    src/
    ├ *.cpp [=> ../build/deps/[debug/release]/*.d; ../build/obj/[debug/release]/*.o]
    ├ *.h
    └ *.rc [Windows Resource script for version information => ../build/windows/[debug/releasse]/*.res]
    doc/ [source documentation generated by doxygen]
    build/
    ├ obj/
    │ └ [debug/release]/
    │   └ *.o
    ├ deps/
    │ └ [debug/release]/
    │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
    └ windows/
      └ [debug/release]/
        └ *.res [Windows Resource file]
    tools/
    ├ bin/
    │ └ [the executable files/tools (Windows, Linux, ...) including DLLs (Windows)]
    ├ share/
    │ └ [project-title]/
    │   └ tools/
    │     └ *.rcc [Qt resource file for tools, contains icons for example]
    ├ resource/ [Icons, ... for the tools; for the generation of the .rcc file]
    │ ├ icons/
    │ └ *.qrc [an XML file listing all files for the .rcc output file => ../share/[project-title]/tools/*.rcc]
    ├ src/
    │ └ [tool-name]/
    │   ├ forms/
    │   │ └ *.ui [QtDesigner files => ../../../build/[tool-name]/ui/ui_*.h]
    │   ├ *.cpp [=> ../../build/[tool-name]/deps/[debug/release]/*.d; ../../build/[tool-name]/obj/[debug/release]/*.o]
    │   ├ *.h
    │   └ *.rc [Windows Resource script for version information => ../../build/[tool-name]/windows/[debug/release]/*.res]
    ├ doc/ [source documentation generated by doxygen]
    │ └ [tool-name]/
    └ build/
      └ [tool-name]/
        ├ obj/
        │ └ [debug/release]/
        │   ├ *.o
        │   └ moc_*.o [translated Qt MetaObject files]
        ├ ui/
        │ └ ui_*.h [translated .ui files for including in the source code]
        ├ moc/
        │ └ [debug/release]/
        │   └ moc_*.cpp [Qt MetaObject files => ../../obj/[debug/release]/moc_*.o]
        ├ deps/
        │ └ [debug/release]/
        │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
        └ windows/
          └ [debug/release]/
            └ *.res [Windows Resource file]
The end user shall receive the bin and share folders.
Maybe the structure is more than good enough and some of you might find it useful for himself.
I ask for feedback smile.png

#2ShyGuy92

Posted 01 August 2013 - 04:22 PM

Hello Guys,

 

I am an experienced C++ programmer and have been using several project structure, like simple src and obj folders and using the command line, default structures provided by IDEs such as the Code::Blocks, etc. With my experience the complexity of my projects grow and again I am thinking of an efficient directory structure for my projects... of course I have already searched the internet, but I didn't find any examples perfectly fitting my needs... so I think, I show you my beta structure to gather opinions, modification and improvment suggestions.

My structure is of course meant to be used for developing platform independent games (mostly basing on SDL, SFML etc.). In addition, most of my projects would also need tools (either command lines, or GUI using Qt) for level editing, file converting etc. Here is my current structure:
 

    bin/
    └ [the executable file (Windows, Linux, ...) including DLLs (Windows)]
    share/
    └ [project-title]/
      └ [all program data, like graphics, level files, etc.]
    src/
    ├ *.cpp [=> ../build/deps/[debug/release]/*.d; ../build/obj/[debug/release]/*.o]
    ├ *.h
    └ *.rc [Windows Resource script for version information => ../build/windows/[debug/releasse]/*.res]
    doc/ [source documentation generated by doxygen]
    build/
    ├ obj/
    │ └ [debug/release]/
    │   └ *.o
    ├ deps/
    │ └ [debug/release]/
    │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
    └ windows/
      └ [debug/release]/
        └ *.res [Windows Resource file]
    tools/
    ├ bin/
    │ └ [the executable files/tools (Windows, Linux, ...) including DLLs (Windows)]
    ├ share/
    │ └ [project-title]/
    │   └ tools/
    │     └ *.rcc [Qt resource file for tools, contains icons for example]
    ├ resource/ [Icons, ... for the tools; for the generation of the .rcc file]
    │ ├ icons/
    │ └ *.qrc [an XML file listing all files for the .rcc output file => ../share/[project-title]/tools/*.rcc]
    ├ src/
    │ └ [tool-name]/
    │   ├ forms/
    │   │ └ *.ui [QtDesigner files => ../../../build/[tool-name]/ui/ui_*.h]
    │   ├ *.cpp [=> ../../build/[tool-name]/deps/[debug/release]/*.d; ../../build/[tool-name]/obj/[debug/release]/*.o]
    │   ├ *.h
    │   └ *.rc [Windows Resource script for version information => ../../build/[tool-name]/windows/[debug/release]/*.res]
    ├ doc/ [source documentation generated by doxygen]
    │ └ [tool-name]/
    └ build/
      └ [tool-name]/
        ├ obj/
        │ └ [debug/release]/
        │   ├ *.o
        │   └ moc_*.o [translated Qt MetaObject files]
        ├ ui/
        │ └ ui_*.h [translated .ui files for including in the source code]
        ├ moc/
        │ └ [debug/release]/
        │   └ moc_*.cpp [Qt MetaObject files => ../../obj/[debug/release]/moc_*.o]
        ├ deps/
        │ └ [debug/release]/
        │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]
        └ windows/
          └ [debug/release]/
            └ *.res [Windows Resource file]

The end user shall receive the bin and share folders.

Maybe the structure is more than good enough and some of you might find it useful for himself.

I ask for feedback smile.png


#1ShyGuy92

Posted 01 August 2013 - 04:20 PM

Hello Guys,

 

I am an experienced C++ programmer and have been using several project structure, like simple src and obj folders and using the command line, default structures provided by IDEs such as the Code::Blocks, etc. With my experience the complexity of my projects grow and again I am thinking of an efficient directory structure for my projects... of course I have already searched the internet, but I didn't find any examples perfectly fitting my needs... so I think, I show you my beta structure to gather opinions, modification and improvment suggestions.

My structure is of course meant to be used for developing platform independent games (mostly basing on SDL, SFML etc.). In addition, most of my projects would also need tools (either command lines, or GUI using Qt) for level editing, file converting etc. Here is my current structure:
 


    bin/

    └ [the executable file (Windows, Linux, ...) including DLLs (Windows)]

    share/

    └ [project-title]/

      └ [all program data, like graphics, level files, etc.]

    src/

    ├ *.cpp [=> ../build/deps/[debug/release]/*.d; ../build/obj/[debug/release]/*.o]

    ├ *.h

    └ *.rc [Windows Resource script for version information => ../build/windows/[debug/releasse]/*.res]

    doc/ [source documentation generated by doxygen]

    build/

    ├ obj/

    │ └ [debug/release]/

    │   └ *.o

    ├ deps/

    │ └ [debug/release]/

    │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]

    └ windows/

      └ [debug/release]/

        └ *.res [Windows Resource file]

    tools/

    ├ bin/

    │ └ [the executable files/tools (Windows, Linux, ...) including DLLs (Windows)]

    ├ share/

    │ └ [project-title]/

    │   └ tools/

    │     └ *.rcc [Qt resource file for tools, contains icons for example]

    ├ resource/ [Icons, ... for the tools; for the generation of the .rcc file]

    │ ├ icons/

    │ └ *.qrc [an XML file listing all files for the .rcc output file => ../share/[project-title]/tools/*.rcc]

    ├ src/

    │ └ [tool-name]/

    │   ├ forms/

    │   │ └ *.ui [QtDesigner files => ../../../build/[tool-name]/ui/ui_*.h]

    │   ├ *.cpp [=> ../../build/[tool-name]/deps/[debug/release]/*.d; ../../build/[tool-name]/obj/[debug/release]/*.o]

    │   ├ *.h

    │   └ *.rc [Windows Resource script for version information => ../../build/[tool-name]/windows/[debug/release]/*.res]

    ├ doc/ [source documentation generated by doxygen]

    │ └ [tool-name]/

    └ build/

      └ [tool-name]/

        ├ obj/

        │ └ [debug/release]/

        │   ├ *.o

        │   └ moc_*.o [translated Qt MetaObject files]

        ├ ui/

        │ └ ui_*.h [translated .ui files for including in the source code]

        ├ moc/

        │ └ [debug/release]/

        │   └ moc_*.cpp [Qt MetaObject files => ../../obj/[debug/release]/moc_*.o]

        ├ deps/

        │ └ [debug/release]/

        │   └ *.d [Dependencies of the .cpp files from the .h files; for Makefile]

        └ windows/

          └ [debug/release]/

            └ *.res [Windows Resource file]

The end user shall receive the bin and share folders.

Maybe the structure is more than good enough and some of you might find it useful for himself.

I ask for feedback smile.png


PARTNERS