Soluling home   Document home

Configuration Change

This message is shown if you try to change the main configuration of a RAD Studio Group file.

Each Delphi VCL project can have any number of configurations (e.g., Debug and Release) and two platforms: 32-bit and 64-bit. Each configuration/platform combination has its output file path. For example, a 32-bit Debug configuration of Project1.dpr produces Win32\Debug\Project1.exe file, and a 64-bit Release configuration produces Win64\Release\Project1.exe. Only one of these possible output files can be the main file. Other output files are platform files. If you change the main configuration, Soluling will swap the main file with the selected platform file, and that has a consequence: The context values in the project will change, making the project dirty. Whenever the content value changes, Soluling creates a new row and then tries you populate the existing translations from the old context. This doesn't always work, and you might lose some translations.

For example, let's have ProjectGroup1.groupproj that contains Project1.dpr and Project2.dpr. A Soluling project tree of that project looks like this.

Our initial configuration is Debug|Win32, and that makes the main files to Project1\Win32\Debug\Project1.exe and Project2\Win32\Debug\Project2.exe. If we now change the configuration to Debug|Win64, the main files will change to Project1\Win64\Debug\Project1.exe and Project2\Win64\Debug\Project2.exe, and two new sub-sources will appear to the project. They are new and marked with yellow dots. The previous (32-bit) sub-sources are still there (Soluling does not remove them, so you can check that the translations were correctly moved.

To remove the unused items, scan again or click Home | Editing | Clear statuses | Remove unused items ribbon button and scan again. Now the unused items are gone.

As you can see, the main files now are 64-bit .exe files.