migrating from ccs3.3 to CCSv5

USHA M said:

While porting CCS3.3 built project in CCSv5, if I build the project some warning is seen saying....
This project contains unresolved buildable linked resources. It might not build as expected.

This warning is saying that the path to some of the resources (source files/include files) linked to the project could not be resolved. I would suggest carefully checking the Project Explorer view and making sure that all the expected source files are part of the project and properly resolved. If they are not resolved, there would be a "!" icon next to the file name indicating that those files have broken links.
Please see this related thread for additional information: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/143695/519348.aspx#519348

USHA M said:

After importing CCS project, migration log will have some warning as below..

!CONFIGURATION: 'com.ti.ccstudio.buildDefinitions.TMS470.Debug.237581937' [Fri Jul 20 11:35:39 GMT+05:30 2012]
!TOOL: 'com.ti.ccstudio.buildDefinitions.TMS470_4.6.exe.compilerDebug.255605943'
!WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.TMS470_4.6.exe.compilerDebug.255605943::-mf
!TOOL: 'com.ti.ccstudio.buildDefinitions.TMS470_4.6.exe.linkerDebug.1781029384'
!WARNING: Unresolved option: com.ti.ccstudio.buildDefinitions.TMS470_4.6.exe.linkerDebug.1781029384::--default_order

These warnings are saying that certain compiler/linker options that were set in the older CCS 3.3 project did not get resolved properly by the newer compiler tools in CCSv5. It is mainly to notify the user that the migrated project does not have the exact same setttings/options as the older project and gives the user a chance to go fix/update them as needed.

The message could be because the option is deprecated/no longer valid, or because it is expecting certain values which it did not before. I know --default_order linker option is no longer valid in the newer ARM codegen tools. The -mf option, I believe, takes a value between 0 and 5. You can go into Project Properties->Build->ARM Compiler->Optimization and adjust the -mf option to what you desire.