This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TI-RTOS project (IAR); absolute paths

Other Parts Discussed in Thread: CC2640

Hi,

I'm in the early stages of setting up a robust build environment for projects to come. These projects are wireless BLE applications (medical devices), using cc2640 MCU on in-house developed pcb's. We are starting development using the cc2650dk evaluation boards though. We have choosen the IAR EWARM compiler/IDE for several reasons. There are multiple developers spread globally that will cooperate on these projects. The plan is to create a version controlled "template" to start the projects off.

So far, I just started to play around with everything and I managed to generated the "empty" project using TI-RTOS (this project is not empty though. It contains a led_blinking task). It compiles fine with IAR and I'm able to debug them using the onboard XDS100v3 emulator.

Now to the question...

Looking at my IAR project, it contains hundreds of absolute paths to folders on my computer. I can see absolute paths to my TI-RTOS installation folder as well as absolute paths within the IAR project itself. This will be ok as long as I'm the only developer and nothing is installed in a different location, but it will break if someone else tries to compile the project. Even if I'm the only developer it will be difficult to maintain since it requires me to clone projects from version control to the exact same location every time. 

What strategy should I use to get projects portable, using relative paths, when setting configurating TI-RTOS and creating the IAR project?

Thanks

//Ola

  • Sorry for the delay. Trying to get a complete answer for you.
  • The way the TI-RTOS examples are imported into IAR is the problem. IAR makes everything an absolute path. Note: we do not ship .eww files. The examples in the SimpleLink BLE SDK does ship .eww files and are created with relative paths. You can try using the BLE SDK examples as the starting point instead of TI-RTOS examples.

    I do not foresee TI-RTOS changing to deliver .eww files. We have too many examples on some many devices.

    You might contact IAR to see if they have any tricks.

    Todd