Generally, migrating from one version of the LPCXpresso IDE to a later version should be straightforward, though you should always browse the release notes, the supplied documentation and online FAQ material.
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 LPCXpresso IDE.
Installation and License
A new version of the LPCXpresso IDE may be installed in parallel with existing installations. This allows a newly released version to be trialed alongside a version currently installed.
Furthermore, there is no need to take any special care with licenses (activation codes), since any installed code will automatically be picked by the new LPCXpresso IDE installation.
Installing Eclipse plugins
If you install a new version of LPCXpresso IDE on Mac OS X or Linux, then the first time you run the new install you will be offered the opportunity to re-install previously used plugins (for example, version control). However this does not happen on Windows and manually installing your favorite plugins may take considerable time to complete.
An alternative approach is to import the plugins from an earlier LPCXpresso IDE installation. To do this follow:
File->Import->Install->From Existing Installation
Then browse to an existing installation's internal lpcxpresso directory (i.e. the directory found within an existing LPCXpresso IDE application's installation).
Import projects into a fresh workspace
Whilst a new LPCXpresso IDE version can open workspaces created by an earlier release, a workspace and the projects it contains that have been used by a new LPCXpresso IDE version may not correctly load into an earlier version. Thus we would strongly recommend that you backup your projects before commencing any migration (just in case).
The simplest way to do this is to create a new workspace in the new LPCXpresso IDE version, then import any projects into this new workspace. How to import projects into a new workspace is detailed in the FAQ Import/Export projects.
Alternatively, if you have your projects checked into a version control system (for example using SVN and the Subclipe Eclipse plugin), then you can simply check you projects out into the new workspace.
You should also ensure that you do a full, clean build after switching to the new version.
Delete launch configurations
Sometimes the contents of or options specified in the debug launch configurations used by LPCXpresso IDE can change between versions. Thus when moving to a new version of the LPCXpresso 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. Note that you may need to reapply any modifications you made to your launch configurations in your previous version of LPCXpresso IDE.
For more information on launch configurations, please see the FAQ Launch Configuration Menu.
The startup code generated by LPCXpresso IDE can sometimes be updated between releases, often to support new tool features. We would thus 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.
In LPCXpresso IDE V7.9.0 and later, the linker script template mechanism has been overhauled to provide a much more flexible and powerful means for the user to change the content of the linker script generated by the managed linker script mechanism.
If you are moving a project that uses a modified linker script from a version of LPCXpresso IDE prior to version 7.9.0, then please read the detailed FAQ on Freemarker Linker Script Templates.