This section will describe the steps necessary to disable SysConfig. Disabling SysConfig may be necessary when freezing source code for production or when you are satisfied with the output.
This example will use the
multi_role project from the BLE5-Stack,
but the steps can be adopted for project.
A summarization of the steps can be found below:
- Build the project at least once so that SysConfig can generate output
- Locate the generated files
- Copy generated files from build directory
- Disable SysConfig from running as a pre-build step
- Modify compiler/linker files to point to moved files
Locating Generated Files¶
The first step to disabling SysConfig is to determine which files it has generated.
<> button in SysConfig to see which files it is currently
generating. See Generated Files for an example of which files
are generated by SysConfig for the
- In CCS these files are placed in
<build_config>is the build configuration of the project. (e.g.
- In IAR these files are placed in the project folder (e.g.
<proj_import>is the location selected when importing the project in IAR
- In the IDE the SysConfig files reside in a virtual folder called SysConfig Generated Files. You can find their location by right clicking any of the files in this folder and selecting “Open Containing folder…”
Copy Generated Files¶
IAR Users may skip this step
In CCS the build directory is cleaned every time the project is rebuilt,
so it is necessary to copy the generated files to a permanent location
before the project is rebuilt. Follow the steps below to do so. We will
place the files in the application in a folder called
syscfg but it
can be called anything.
- Right click on the project -> New -> Folder
- Copy the files from
<build_config>/syscfgto the new folder.
- See Generated Files to see which files to copy
Disabling SysConfig is slightly different for IAR vs CCS. Expand the relevant section below to see how to disable SysConfig.
In IAR, SysConfig is treated as a Custom Build step. To access the custom build steps select Project > Options > Custom Build. Remove all the fields that are populated under the Custom Tool Configuration tab as shown below:
In CCS, files ending in
.syscfg are automatically flagged as
SysConfig files. If you have a file active in your workspace, it will
invoke the SysConfig tool. This can be disabled by excluding
.syscfg files from build.