Large Projects
-
I am after info on the best way to structure a large MFC/C++ project, addressing the following points:
- Fastest Compilation Speed
- Minimal dependencies
- Minimal knowledge required to add new classes, i.e. no need to remember all the include files involved
The application consists of about 7 Dll's, each containing related functionality (windows, core, document, reporting) Most new development requires the use of the main Dll's.
-
I am after info on the best way to structure a large MFC/C++ project, addressing the following points:
- Fastest Compilation Speed
- Minimal dependencies
- Minimal knowledge required to add new classes, i.e. no need to remember all the include files involved
The application consists of about 7 Dll's, each containing related functionality (windows, core, document, reporting) Most new development requires the use of the main Dll's.
The Holy Trinity of large projects!! Here is the best single suggestion I can make: Avoid including headers within headers....I made this mistake with my first large C++ project, and as time went on I realized that any change I made to a header (like adding a new method) had the potential to cause recompiles across the application. To support this, you'll need to replace the member variable object definitions within your classes with pointer or reference members.