New build setting CCS 11.1

Steffen Fuchs

Other Parts Discussed in Thread: CCSTUDIO

Hi,

I`ve got the same problem as described here: https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/1067522/ccs-failed-to-build-with-new-build-configuration

I`ve setup a new project with CSS V11.1, copied c./h. files from the existing project and got it compiling. Than I setup a new build target by copining the existing one.

Result is a empty makefile!

Thanks

Best regards

Steffen

over 3 years ago

0 Ki over 3 years ago

TI__Guru**** 471861 points

Hello Steffen,

Can you provide a test case as mentioned in my last post in the other thread?

Thanks

0 Steffen Fuchs over 3 years ago in reply to Ki

Intellectual 685 points

I´ve stripped out all of the source code from my example: MIM-Processing-G2.zip

The build target Release V2.0 is a rename of the standard release target that you get when you make a new project in CCS. This compiles.

The V2.1 target ist a copy of V2.0 via manage build targets. This doesn´t compile and generates a empty make file. You can add your own build target. I`ve tried it many times with different names, with restart of CCS, etc, etc,

0 Ki over 3 years ago in reply to Steffen Fuchs

TI__Guru**** 471861 points

Thank you for the test case. I can reproduce the issue.

I have some questions about how this project was created:

Steffen Fuchs said:
I`ve setup a new project with CSS V11.1, copied c./h. files from the existing project and got it compiling.

Was the this project a new project that was created from scratch with CCS 11.1? This project was NOT originally created with an older CCS version and then imported to CCS 11.1, correct?

Steffen Fuchs said:
Than I setup a new build target by copining the existing one.

New CCS projects are created with default Debug and Release configurations. Yours has neither. I assume that you either: a) renamed one of the default configurations to "Release V2.0 (HW V1)" and deleted the other configuration... or b) created a new conifguration called Release V2.0 (HW V1), which was copied off one of the default configurations, and then deleted both remaining Debug and Release configurations.

Then you tried coming the remaining configuration and ran into the error.

Assuming it is either a or b, which step did you use?

Thanks

0 Steffen Fuchs over 3 years ago in reply to Ki

Intellectual 685 points

1) The project was created with CCS 11.1 from scratch.

2) I`ve deleted the debug target and renamed the release target to Release V2.0 and than I`ve copied it into Release V2.1.

0 Ki over 3 years ago in reply to Steffen Fuchs

TI__Guru**** 471861 points

Thanks. I tried the same steps with my own project in CCS 11.1 but I can't reproduce the issue. I have sent your project to engineering for further analysis. I will pass on any updates as I receive them.

Thanks

+1 Ki over 3 years ago in reply to Ki

TI__Guru**** 471861 points

Engineering has found a different bug with CDT that is the root cause of this issue. Apparently it only affects project that have the Hex Utility enabled.

To "repair" the project, see the engineer's comments below:

the project can be manually recovered by replacing line #120 in file MIM-Processing-G2/.cproject from the original:

to:

It has to match the ID on line #197.

Thanks

0 Ki over 3 years ago in reply to Ki

TI__Guru**** 471861 points

A bug has been filed for this issue. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-10761

Thanks

Code Composer Studio™︎

Code Composer Studio forum

New build setting CCS 11.1