converting a big project from IAR to CCS - how?

Porting from one toolset to an entirely different one is never simple.

I don't know of any automated tools; it would obviously not be in IAR's interest to provide such a thing, and probably wouldn't be worth the effort for TI (and they might be mindful of their relationship with IAR, anyhow...)

Porting requires a thorough understand of both the original toolset and the new toolset - so a lot of study of manuals is, I'm afraid, unavoidable.

As a start, I would check your IAR documentation to see if there is an option to disable all its extensions and special features - then use this to get your code to a point where it is "pure ANSI". You should then, at least, be able to get it to compile on another toolset.

Then there's the question of your source code: has it been carefully written to be portable - or is it deeply entwined with IAR-specifics?

If the code is not carefully written to be portable,  it may be better to start by making it portable in IAR, and then moving the result to CCS...

Thanks for the quick response. My code doesn't use any IAR specifics and is almost all pure ANSI C, so i was more wondering about how to convert project settings from IAR to CCS.

Rene Limberger said:

how to convert project settings from IAR to CCS.

This is where "a thorough understand of both the original toolset and the new toolset " comes in!

• You need a thorough understand of IAR in order to be sure of what all the current settings do;
• You need a thorough understand of CCS in order to know how to achieve those same things in CCS.

I think you're just going to have to go through each setting in each dialogue, and convert each one over to CCS.

A fundamental flaw with all GUI IDEs that I've ever used is getting them to produce a full listing of all the sttings used. It usually just comes down to taking screenshots of the dialogues!

Usually, compiler listing files show the active option settings - so that might help you...