This question already has an answer here:
- Project structure and folder naming 1 answer
I'm currently working on a C++ project in Visual Studio and can't make up my mind on how I should be organizing my files. As of currently, my file directory looks similar to the following.
->source -> game ->file1.cpp ->file1.h ->file2.cpp ->file2.h ->... -> libraries // usually reserved for external libs ->lib1 ->file1.cpp ->file1.h ->lib1 ->include // header files ->lib // compiled .libs & .dlls ->visual studio -> // visual studio project stuff
I will be the first to admit that I haven't put too much thought into how everything should be organized. My philosophy for the "source" folder is to contain any source code or compiled libraries that will be included in my Visual Studio project. However, I could see this folder getting messy after a while. I also know that some people separate header and source files into different directories, but this just seems like extra folder navigation without much benefit.
I'm curious if there are any standard methodologies for organizing Visual Studio projects. I would like to avoid the huge organization refactor later down the road.