Support relative paths when targetting MDK-ARM toolchain

[vchatelain]

Using "Firmware Relative Path" currently have 2 problems:

• The path in the text field is displayed as absolute while the actual path is stored in the .ioc file as relative
  • This is somewhat confusing to the user as CubeMX will display different (absolute paths) for different users with the same .ioc file.
• Targetting the MDK-ARM toolchain will generate/update an .uvprojx file with absolute paths and not relative paths
  • This is an issue when the firmware is stored in a vcs repository and share among several developpers which don't have their local copy at the same location. For each developper re-generating code with CubeMX, absolute paths on its computer will be appended in the Keil file. Therefore we need to manually remove them in the .uvprojx file before commiting our changes to the repository.

Would it be possible to use relative paths instead (or support them alongside absolute paths) in CubeMX and uVision project file ? Looking at other posts in the community, it seems CubeIDE has the same issue.

[Ghofrane GSOURI · Accepted solution]

Hello @vchatelain 

A change request has been raised to dev team for feasibility check.

Internal ticket number  205362 

I will keep you posted with updates.

THX

Ghofrane 

[vchatelain]

Thank you for the quick response !