Hi There,
When I migrate projects from DS-5 to ARM Development Studio 2022 or 2023, I get following issues:
1) Warning: Orphaned configuration. No base extension cfg exist for com.arm.eclipse.build.config.baremetal.lib.debug.xxxxxxxxx
2) Some of the macros defined in Preprocessor tab for the whole project are missing for some sub-directories, and compiling errors will generated without adding them one by one to those sub-directories.
Please help to see if any solutions for these.
Thanks
Hi1) Orphaned configurations can sometimes occur when the original DS-5 project is slightly/unknowingly broken, and the DS-5-to-ArmDS project migrator is unable to fix-up the issue. This might happen if a specific version of Arm Compiler is selected for a project instead of the default Arm Compiler. Which version of Arm Compiler are you using?What is the complete version of the warning? (I need to see the bit that you've shown as xxxxxxxxx).Do you see two sets of numbers at the end, e.g.:com.arm.eclipse.build.config.baremetal.lib.debug.1234567890.2345678912) I suspect that the missing macros are caused by the orphaned configuration above.Let's try to fix the orphaned configuration first.Stephen
Hi Stephen,
The complete warning message in 2023.1 is:
Orphaned configuration. No base extension cfg exists for com.arm.eclipse.build.config.baremetal.exe.debug.194745424.949978659
During migration, I upgraded the toolchain from Arm Compiler 5 (DS-5 build-in) to Arm Compiler 5.06.7 (installed to Arm Development Studio), instead of migrating to Arm Compiler 6.
Ok, thanks. To fix this issue, you'll need to manually edit the .cproject file:1. Remove the current (broken) migrated project from DS2. Open the original (DS-5 version of) the .cproject file in a text editor (keep a backup!)3. Locate <configuration> elements with the id attribute: com.arm.eclipse.build.config.baremetal.exe.debug.194745424.9499786594. Edit all those ids to remove the '.194745424' parts, so you end up with: com.arm.eclipse.build.config.baremetal.exe.debug.949978659Then import the modified project into DS. The migrator should run and update the project to work with DS.Let us know how you get on.Stephen
Thanks for the info. Followings are my results:
1) If modifying DS-5 .cproject file with removal of ".194745424.", after importing it to ADS 2023, the all the configuration IDs in the new .cproject file would be changed to ".949978659.75773413" by IDE with another lay of digital strings appended, and still I got warning of "Orphaned Configuration".
2) If modified this new .cproject file of ARM Development Studio by removing all ".949978659", and reloaded it in ADS, the warning message still showed up.
BTW what do these digital IDs mean?
Hi againSorry to hear that didn't work for you.I suspect the issue is related to the switch from "Arm Compiler 5 (DS-5 built-in)" which you had for your DS-5 project, to the "Arm Compiler 5.06.7" that you have installed to Arm Development Studio.In your original DS-5 project, do you have any build configurations for anything other than "Arm Compiler 5 (DS-5 built-in)"? If so, they could result in an orphaned configuration during migration to Arm DS, so try fixing then to use "Arm Compiler 5 (DS-5 built-in)".Another user had a similar issue and was able to resolve it by rebuilding the configurations - see the end of
https://community.arm.com/support-forums/f/armds-forum/54622/armds_idec-java-was-started-error
Please try the above suggestions. If you are still not able to resolve the issue, then please "Open a Support Case" from the Support > Arm Support Services at the top of this web-page. You will then be able to send us your .cproject file to examine.Stephen