CCS: dummy file added during legacy v.3.3 project import

Could you attach the complete build log for us to review please (https://software-dl.ti.com/ccs/esd/documents/sdto_ccs_build-errors.html#ccs-build-console)? 

So there is no dummy.obj (either auto-generated or manually added) anywhere inside the project path but it is still getting pulled into the link?

Hello!

I am sure there was nothing like dummy in .pjt file being imported. However, after import I see picture like this:

When I try to build this project, I get error about multiple _main symbols, as in bld_dummy_1.log. If I try to rebuild, I am getting even more strange error, like in bld_dummy_2.log.

What makes me crazy, I have imported this project before and managed to build at least C_Debug configuration. Now I have to trace back through multiple revisions, so I have checked out repository to the separate location, renamed .pjt file, as Eclipse is unhappy about multiple projects with same name, and try to import. The rest you know already.

Would appreciate any hint.

Thank you.

bld_dummy_1.log

bld_dummy_2.log

One more observation

It looks that generated assembly files in asm subfolder are marked as excluded from build in the project, which was imported succesfuly, but look as build input files in failing one.

From the build logs, it does look like the .asm files generated by the compiler and then being recompiled as though they were source files. This should not be happening for generated assembly files. Looks like some setting is not interpreted properly during migration.

Would you be able to share the project that demonstrates this issue so we can reproduce the problem and identify root cause? If could also attach the original CCS 3.3 .pjt file that would be helpful as well.

This issue is being worked offline.

After offline discussions it was agreed upon that OP will try to manually recreate the project in CCSv10, and this thread can be closed. If he encounters issues with the new project he will create a new thread.