HyperMake™ uses multiple threads when compiling C, C++, Pascal, Assembler and Resource files. The developer’s computer runs at the optimum level to get files compiled as quickly as possible. HyperMake™ is extremely intelligent with regard to thread management and system resources and even if a build is in progress the developer can still have full use of the machine to engage in other tasks.

HyperMake™ has a remarkably efficient make system and detects immediately everything that needs to be compiled by monitoring all projects registered via the C++ Builder^® IDE or the HyperMake™ command line tools. This monitoring provides for many additional features within C++ Builder^®, for example a progress bar during the compilation process so the developer knows exactly how far through the make process they are.

HyperMake™ also has a high performance dynamic file caching system that is superior to the MS Windows disk caching system and even outperforms compiling directly from a RAM disk. Being dynamic this caching system has a significant advantage over a static RAM Disk in that it only uses the memory required for the build rather than having to reserve enough to guarantee the RAM disk will be large enough for any build possible. HyperMake™'s file caching system is fully automatic and self maintaining, releasing resources when projects aren't compiled for a certain amount of time.

HyperMake™ supports Pre-Compiled Header File Injection. This allows the user to setup a single header file listing all the shared include files that are used throughout the project. HyperMake™ will then inject it into each of the source files providing faster compilation and smaller pre-compiled header files.

HyperMake™ contains HeaderGuard, a system that monitors Pascal generated header files to see if they have really changed. Often when a package is built and installed, C++ Builder^® will regenerate the HPP header files during every build, which in turn causes all the C++ dependant files to be recompiled. HyperMake™ monitors these files and checks to see if they have really been modified and only permits updating when necessary. This produces a substantial reduction in the number of files recompiled as C++ Builder^® frequently encounters situations where it believes these header files have changed.

In addition HyperMake™ provides protection against numerous compiler bugs with AV Guard. C++ Builder^® is notorious for Access Violations, which are frequently due to previously compiled files leaving the compiler in an indeterminate unstable state. This normally requires the IDE to be restarted. HyperMake™ monitors for these Access Violations and restarts the IDE compilers when an Access Violation occurs. HyperMake™ then signals the IDE to recompile the source file and continue with the build process. All this is entirely transparent to the developer.

HyperMake™ also rectifies several resource compiler problems found in C++ Builder 6. Builder 6 fails to pass all of the compiler options accross to the resource compiler. HyperMake™ intercepts each C++ Builder6 resource compile and corrects the compiler options ensuring the resource file is generated properly.

BuilderBooster™,HyperMake™,ActiveCompile™ and RemoteBoost™ are trademarks of
First Degree Systems Ltd. C++ Builder^® is a registered trademark of Borland Software Corporation.