|Deletions are marked like this.||Additions are marked like this.|
|Line 34:||Line 34:|
|When upgrading the Code Red IDE v5, you may need to fixup error parsers in existing projects to prevent make errors being left in the Problems View when builds succeed. For more details, please see the FAQ:||When upgrading to Code Red IDE v5, you may need to fixup error parsers in existing projects to prevent make errors being left in the Problems View when builds succeed. For more details, please see the FAQ:|
Migrating existing projects to a new version of the Code Red IDE
This FAQ provides a number of hints and suggestions of things that you should do or consider when migrating to a new version of the Code Red IDE (including Red Suite and LPCXPresso). These are primarily focussed at moving between major releases (for example, upgrading from Code Red IDE v4.x to v5.x), but it is good practice to consider taking some of these into account when moving between minor releases too (for example, updating from Code Red IDE v5.a.b to v5.x.y).
Generally migrating an existing project from one (major) version of the Code Red IDE to a later version should be straightforward, though you should always browse the supplied documentation and the online FAQs. However there are a number of things that we recommend that you do when carrying out such a migration.
Import projects into a fresh workspace
When moving to a new Code Red IDE version we strongly recommend that you create a new workspace and import the projects into the new workspace. Whilst a new Code Red IDE version can open workspaces created by an earlier major release, a workspace that has been used by a new Code Red IDE version may not correctly load into an earlier version.
It is also important that you take a backup copy of your projects before starting the upgrade of your projects.
Thus for example we would not recommend trying to open a workspace that has been created/edited in Red Suite 5 with Red Suite 4.
How to import projects into a new workspace is detailed in the FAQ Import/Export projects.
Recreate launch configurations
When moving to a new version of the Code Red IDE, we would recommend deleting any debug launch configurations within your project which were created by an earlier version. These files are typically named "<projectname> Debug.launch" and "<projectname> Release.launch"). The easiest way to do this is to right click on the project in Project Explorer and select
Launch Configurations -> Delete Launch Configurations
from the context sensitive menu. The IDE will then automatically create a fresh set of launch configurations the next time that you start a debug session.
More information on launch configurations, please see the FAQ Launch Configuration Menu.
Fixup error parsers
When upgrading to Code Red IDE v5, you may need to fixup error parsers in existing projects to prevent make errors being left in the Problems View when builds succeed. For more details, please see the FAQ:
We would strongly recommend that you consider updating your startup code to match the latest generated by the project wizard for the part that you are using. This is particularly the case if your project was originally created by Code Red IDE v3.5.x or earlier (or 3.7.x in the case of LPCXpresso for Linux).
This will help to avoid potential problems with the enhancements made to linker scripting (as described in the FAQ Enhanced Managed Linker Scripts) as well as C library interaction (as described in the FAQ Redlib v2 Notes).
Convert from CMSIS 1.3 to CMSIS 2.0
If you are using CMSIS, you may wish to consider migrating your projects to CMSIS 2.0 (or later). For more details see the FAQ Support for CMSIS.