CCS/SM320F28335-HT: Build result of the CCS is dependent on project path

Hi Stephan,

What are the other changes? It see a couple other differences in WinMerge. Can you just attach both files?

Todd

The section xdc.meta contains the absolute path to a generated config C file. That file is located in the subdirectory Debug/configPkg/package/cfg of the project's top directory, and it's name has the application name embedded in it. A change in the application's name will then change the content and size of xdc.meta.

Hi Sasha.

Thanks for your support. I understood now why the build is path dependent, but it also generates new questions:

Why is the absolute path part of the xdc.meta information?

Is it possible to disable this feature?

Is it possible to put it to relative path?

May this"feature" be changed in a newer version of the CCS?

Thanks and Regards

Stephan

The purpose of the absolute path is to be able to find various configuration files even when the actual executable is moved around, possibly to a location where the original relative path wouldn't lead to the configuration files. It's not very likely that we will remove that feature because it is being used by ROV. If you don't care about ROV, you could adjust your build and avoid the section xdc.meta completely, but to help you with that I would have to know more about your build setup.

Alternatively, for any kind of app comparisons we recommend using objdiff utility from software-dl.ti.com/.../index.htm. It ignores meta sections that are not downloaded to the target, and xdc.meta is a meta section.

See also this thread for more info: e2e.ti.com/.../578303