Before using opCpp's SourceGlob feature, you have to ask yourself:
Does your project use shared headers?
Do small source files have large header parsing overhead?
Do you tend to use less code files even though you don't like to?
If you answered yes to these questions SourceGlob could
be an answer to your compile time length issues.
Integrating
In fact it's also the easiest way to integrate opCpp into your build process.
Using SourceGlob:
- feed sourceglob source file path patterns ... or ...
- feed sourceglob your opcpp output path
- sourceglob will output a cpp file that includes all your source files.
- make sure sourceglob is called once per build
- make sure the glob file is compiled into your project (makefile, visual studio)
The sourceglob will get recompiled any time a dependency changes,
and theres no worrying about feeding in opcpp output either.
Pretty Simple Huh?