Very similar question and good answers here: #include all .cpp files into a single compilation unit?
The summary seems to be that less I/O overhead is the major benefit.
See also The Magic Of Unity Builds as linked in the above question as well.
More Related Contents:
- "imspossible" error on a simplest code [closed]
- String return from member function in C++
- Compilation error: expected constructor, destructor, or type conversion before ‘;’ token [closed]
- Error when building a C++ program for the second time [closed]
- Why does changing 0.1f to 0 slow down performance by 10x?
- How to enable C++17 compiling in Visual Studio?
- Why does C++ compilation take so long?
- C++, variable declaration in ‘if’ expression
- How to recompile with -fPIC
- Mismatch Detected for ‘RuntimeLibrary’
- Can I compile all .cpp files in src/ to .o’s in obj/, then link to binary in ./?
- How to compile Qt 5 under Windows or Linux, 32 or 64 bit, static or dynamic on Visual Studio or g++
- Parsing strings of user input using the cparse library from git
- Compile the Python interpreter statically?
- Compiling a static executable with CMake
- Undefined reference error for template method [duplicate]
- Profiling the C++ compilation process
- questions about name mangling in C++
- Skipping Incompatible Libraries at compile
- Using CMake to generate Visual Studio C++ project files
- run a program with more than one source files in GNU c++ compiler
- How do YOU reduce compile time, and linking time for Visual C++ projects (native C++)?
- Pros & Cons of putting all code in Header files in C++?
- Broken c++ std libraries on macOS High Sierra 10.13
- Why does a function declaration with a const argument allow calling of a function with a non-const argument?
- Can I use Qt without qmake or Qt Creator?
- C++ How to compile dll in a .exe
- Why is this C++ wrapper class not being inlined away?
- Difference between CC, gcc and g++?
- What is the difference between “Include Directories” and “Additional Include Directories”