Project Configurations are incorrect when importing from CCSv3.3 to CCSv4

Aaron,

Any chance you could attach the original project?  I just tried this with a couple of 3.3 examples I had and I found that files were getting excluded properly per config and that the options match what they were in the original configs.  However my projects were pretty simple examples that we had in the 3.3 product.  I tried both options of copying into my workspace and leaving in the original location and both worked fine for me

Was there any extra information in the migration.log file that gets generated?

Regards,

John

Hi Aaron,

I have the same OS and CCS build. When importing a 3.3 project with multiple configurations and files being excluded on a per config basis, all those setting are still respected after the import into v4. A small test case (stripped down 3.3 project that can still reproduce the error) would be very helpful in getting to the bottom of this.

Thanks

ki

Hi John,

I tried to attach the .prj file from CCSv3.3 and I will paste the contents of the migration.log below.

Thanks,

-Aaron

!WARNING: Reference to the legacy 'Install_dir' macro detected.  This reference has been replaced with new macro 'CCSv3_INSTALL_ROOT', resolving to a local CCSv3.x installation which has been found at 'C:/CCSTUD~1.3' (Window > Preferences > C/C++ > Managed Build > Macros).  It is recommended, however, that you do not reference any resources from the legacy CCSv3.x installation - consider copying these resources into a product-independent location, and referencing them using a new user-defined macro.

!WARNING: Reference to the legacy 'Install_dir' macro detected.  This reference has been replaced with new macro 'CCSv3_INSTALL_ROOT' (Window > Preferences > C/C++ > Managed Build > Macros).  It is recommended, however, that you do not reference any resources from the legacy CCSv3.x installation - consider copying these resources into a product-independent location, and referencing them using a new user-defined macro.

!ERROR: java.lang.NullPointerException

at com.ti.common.managedbuild.core.util.CTIManagedBuildCoreUtils.unquote(CTIManagedBuildCoreUtils.java:1152)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.resolvePathOptionValue(LegacyProjectImporter.java:1369)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.adjustRelativePathOptionSettings(LegacyProjectImporter.java:1312)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.processFileSettings(LegacyProjectImporter.java:968)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.processBuildConfigurationSettings(LegacyProjectImporter.java:809)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.createManagedMakeProject(LegacyProjectImporter.java:449)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.doRun(LegacyProjectImporter.java:259)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.access$0(LegacyProjectImporter.java:211)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter$1.run(LegacyProjectImporter.java:201)

at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)

at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719)

at com.ti.ccstudio.managedbuild.core.legacy.LegacyProjectImporter.run(LegacyProjectImporter.java:199)

at com.ti.ccstudio.managedbuild.ui.wizards.importlegacy.ImportLegacyProjectWizard$1.run(ImportLegacyProjectWizard.java:107)

at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)

Hi John and Ki,

I was able to reproduce this issue with a simple test project using all the options in my original project except for the include paths.  I attached a zip of the CCSv3.3 project .

-Aaron

Thanks Aaron.  Using this our build guy can see what the problem is.  He is going to try to get it fixed for the 4.1.3 update.

Regards,

John