Files and settings (such as header include paths, compiler Defines, etc.) from a user’s build system need to be consumed into a Helix QAC project – this process is called Project Synchronization. Given the wide and varied tools and methods available for a user to build their software, there are several synchronizations methods available to cover the build landscape. Some are more automated than others and some have limitations, but a user should be able to use at least one of the methods no matter which build system they use.
There are broadly 3 categories of synchronization methods available: Build Monitoring, Automatic Conversion, and Manual.
It is possible to automatically generate a CCT as part of the synchronization process. When this option is used, the synchronization will additionally create a suitable CCT based upon information found.
To generate the most accurate CCT it is recommended to use INJECT. Some synchronization methods, such as JSON and Build Log can generate a CCT, but may not have the full capabilities of the underlying compiler available and may produce a lower quality CCT. Refer to Auto CCTs for more details.
- Synchronization via QA·GUI
- Synchronization via QA·CLI
- Build Monitoring Synchronization
- Automatic Conversion Synchronization
- Synchronizing a Visual Studio Project
- JSON Compilation Database
- Bazel
- Build Log
- Manual Synchronization
- Synchronization Options