The build time for large projects with many source files and build options can be greatly impacted by various security software running on the machine. Some optimizations can be done within CCS to help alleviate this issue.

1. Build-output verbosity affects build-time. For rule commands, gmake writes each command into a temporary .bat file, then runs that .bat file. Switching to 'super-quiet' removes a few 'echo' commands for every compiled file. Today, build-output verbosity can only be set in workspace preferences. It should be allowed to also implement support for setting it per project. Also, support the ability yo add a new 'automatic' build-verbosity mode, which would auto-reduce verbosity based on project size. This 'automatic' mode should be the default.
2. Long compile commands affect build-time. CCS currently handles long compile commands by generating a few additional commands for each compile rule - these commands write all flags into a temporary .opt file, then run the compiler with that .opt file. This is a bit inefficient because all this is done at build-time, for each compiled file. This can be improved by pre-checking just the compiler include-path, and writing only the include-path into a separate .opt file during makefile-generation.