Install Secondary Windows

This is an old revision of Install Secondary Windows, edited by Martin at . The current revision is 150643.

/* What to test */

Installing and testing a new Lazarus Version on Windows

This page describes how to install a 2nd (or 3rd) version of Lazarus on windows. The secondary install is made independent of your existing install.

Backup (optional, but recommended)

No matter if you are here to install a new version of Lazarus or not, it is recommended that you regularly backup your data.

IDE Settings

For the IDE you should backup your settings. Those are stored in the "primary config path" (also known as "PCP"). You can find this folder by opening "About IDE" from the menu "View", sub-menu "IDE Internals":

"About Lazarus" in menu "About Lazarus" window

Projects

Either

Installing a 2nd Lazarus version

Installation

The Windows installer will do all the necessary setup for you.

  • Chose your language.
  • Then click "Next" in the welcome screen.
  • Chose a folder for your new Lazarus install.
    This should be a new empty folder.
  • Check the box "Create a new secondary installation"
  • Click "Next"

If you get a question about "uninstalling" then you have made a mistake.
Cancel the install and try again.

  • The next page will show where your IDE config will be stored.
    This is the "Primary config path" (see "Backup" above)
    You can leave this as given by the installer.
  • Optional: If you wish you can change this path. It should point to an empty folder.
  • Click "Next"
  • On the "Select Components" page un-check the box "Associate file extensions"
    This will automatically uncheck all the extensions in the list.
  • Click "Next"

There will be a pop-up that the file extensions are already set.

  • They are set to your existing installation.
  • They will be kept with your old/existing Lazarus
  • This pop-up is a shortcoming of the installer.

  • There are a few more pages in the installer.
    Confirm all of them with "Next"

First run of your secondary Lazarus install

Time to start your new Lazarus.

  • The IDE will start with a "setup" prompt.
  • Chose you preferred IDE Style (docked or floating)
  • You can look at the other tabs in the setup.
 * It shows the "Lazarus" folder that you had chosen during install.
 * Compiler and sources will be in sub-folders.
 * Debugger will be "FpDebug".

There should be no warnings or errors (red or yellow marks) in the setup.
If there are close the window with the "X" cross, or Alt-F4

  • Press "Start IDE" and Lazarus will start normally.

You can always check "About IDE" (see Backup) to ensure you are using the Lazarus with the correct config path.

You can also edit the "Title" of the Lazarus IDE (under menu: Tools > Options > Environment > Window: "Custom IDE Title". Or you can change the colors of the Source editor. This allows you to quickly identify which setup you are currently using.

Testing projects - using "Publish"

Newer versions of Lazarus can save projects in a different format. While they can be configured to use a compatible format, for testing you should use copies of your project.

Step 1: Create copy - Using your old/existing Lazarus IDE

Open your old/existing IDE.

Now a copy of your project is in the new folder.

"Publish Project" in menu "Publish Project" window

Step 2: Open the copy in the new secondary install

Now you can start your new Lazarus installation.

Don't forget, any change you make will not be in your original project.

What to test

Once you have finished the above steps you can test that everything works as you expect.

  • Compile your app, and test if it functions as before.
  • Run test cases
  • Any other checks...
  • Open and edit your forms in the designer
  • Navigate your sources in the Editor
  • Test tools you often use in the IDE
  • Debug the app in the IDE
  • Check with heaptrc (if you did in the old IDE, and your app was not leaking)
  • ...

You may also want to test creating a new application. If you use templates for new apps then check those too.

Experts only

The below tests are for experienced users only. We do not recommend them unless you fit the description.

*The below tests require frequent changes between the different installed IDE, and additional refined tracking which copy of which project was used for which test. Loosing track of this, can easily mean that development meant for one copy of a project is accidentally made on another copy. * We recommend that this testing is only done if all data is kept in revision control, and you are experienced with using the rcs of your choice, as well as having experience with the Lazarus IDE>

If you already use several Lazarus versions, or plan to do so for reasons other than testing then you might additionally want to test project compatibility between versions.