Possible solutions
The following are several recommended practices to optimize and reduce the build time of the TASKING compiler project:
- Use a workstation with a multi-core CPU and a large amount of PC RAM (32 GB+ is beneficial) to take full advantage of concurrent processing capabilities.
- Store source files, header files, and intermediate build artifacts on a local Solid-State Drive (SSD) for faster read/write access during the build process.
- Configure the antivirus software to exclude directories with build-related files to minimize interruptions and latency.
- Exclude necessary build executables such as C/C++ compiler, assembler, and linker executables, from real-time scanning.
- When using a multi-core system, configure the build process to run in parallel, which allows individual cores to compile separate source files simultaneously. For example, with the TASKING make tool (amk.exe), you can use the -j<number of cores> option to specify the number of parallel jobs. Note that if a build server license is in use, make sure the number of parallel processes does not exceed the licensed limit.
- Generate only the necessary files that are required for the current build. For instance, assembler-generated listing files are typically necessary during verification builds and can be skipped for test or debug builds.
- Restrict map file output to necessary formats. Since the linker can produce a map file in both text and XML formats, generate only one format (for example, for verification purposes) and disable the other one.
- Review the required content within the map file, as it can be configured to include only the necessary information. A map file of a large project may have a significant size of 100 MB+.
For more information, you can refer to the chapter Influencing the Build Time in the TASKING product user guide.