LAUNCHXL-CC1310: Proper way to create and maintain builds with different source paths relative to CCS project

Tool/software:

Hi there!

The goal is to create a CCS project where I can build an app for different boards, for example the actual board as well as a LaunchPad for debugging convenience. The selection should be made with a different build configuration, for example BUILD_LAUNCHPAD or BUILD_ACTUAL_BOARD.

Here is an example project that I created in CCS 12.8.1.00005 for a CC1310-LAUNCHXL:

ccs_build_test.zip

The directory tree is as follows:

├───app
│   ├───.launches
│   ├───.settings
│   ├───BUILD_ONE
│   │   └───lib
│   │       └───one
│   ├───BUILD_TWO
│   │   └───lib
│   │       └───two
│   └───targetConfigs
└───lib
    ├───one
    └───two

I created 2 build configurations: BUILD_ONE and BUILD_TWO. Then I linked the lib folder with a relative path to the CCS project:

Properties for ccs_build_test > Paths and Symbols > Source Location > Link Folder ... > Link to folder in the file system:

Now folder "lib/one" and folder "lib/two" is listed and I have to exclude "two" from the build:

The whole procedure of setting up a linked folder and excluding folders work fine as long as I have a single initial build configuration. After setting up BUILD_ONE I can create a new BUILD_TWO as a copy from BUILD_ONE and set that up too.

BUT! As soon as I try to retrace my steps or change the linked folders then CCS / Eclipse gives me the run around with a linked resource ("lib") that already exist. If I delete the linked resource ("lib") then it is deleted for the other build configuration too and it's back to step one.

In short: what is the recommended way to create and maintain multiple builds with different source paths relative to CCS projects? To be clear BUILD_ONE must use ../lib/one and BUILD_TWO must use ../lib/two

Thanks in advance,

Pieter