Version: **
Question:
Why does my legacy BTSDK project (version 2.7.1 or older) fail to build in ModusToolbox™ 2.4?
Answer:
There have been changes with the build system in more recent versions of the software that affect older projects. You may see errors like the following:
COMPONENT_fw_upgrade_lib/ota_fw_upgrade_common.c: In function 'wiced_ota_fw_upgrade_init':
<command-line>: error: 'DLConfigSSLocation' undeclared (first use in this function)
COMPONENT_fw_upgrade_lib/ota_fw_upgrade_common.c:204:26: note: in expansion of macro 'SS_LOCATION'
204 | nv_loc_len.ss_loc = SS_LOCATION;
| ^~~~~~~~~~~
<command-line>: note: each undeclared identifier is reported only once for each function it appears in
Workaround:
- Identify the location of the current BSP:
- Open the modus-shell terminal and navigate to the application folder.
- Run the following:
make get_app_info | grep 'SHAREDLIBS='
- Look for the following output with the path relative to the application folder. For example:
./../../../wiced_btsdk/dev-kit/bsp/TARGET_<bsp_name>
That is the location of the active BSP.
- Navigate to the folder discovered in step 1c.
- Edit the BSP Makefile. This file is located in the BSP folder and named after the BSP name. For example: <bsp_name>.mk
- Search in the file for the comment line:
# split up btp file into "x=y" text
- Place the following lines immediately above that comment line:
CY_EMPTY=
CY_SPACE=$(CY_EMPTY) $(CY_EMPTY)
- Save the file and retry to build the project.
The legacy project should build successfully in the ModusToolbox™ 2.4 environment.
