|
|
|
|
|
|
|
|
|
|
- Overview
- Principle
- What is a patch?
- Operating mode of patches
- Limitations
- Recreating an executable
- Patches and branches of SCM
Once an application was installed, the application library had to be reinstalled whenever a modification was performed (WDL file). This operation can be tedious, for example: - when the modification affects a single window out of 500 application windows
- when updating the application by Internet, because of the library size.
Additional resources (windows, states, etc.) can be delivered in the form of a patch.. Patches are additional libraries. If the executable has been created with the "Executable will take patch updates into account" option, when the application is launched, the items in the patch will replace those in the application library. What is a patch? A patch is an additional library that contains the elements that will replace elements found in the source library. A patch does not necessarily contain all the elements of the source WDL: only the modified elements are needed. The patch files names respect the following format: <Name>.<WDL>.NNN (example: Application.WDL.001, Application.WDL.002, ...). Operating mode of patches A patch is automatically loaded when loading the library (WDL file) or when loading the executable that includes the library. To do so, the physical file corresponding to the patch must have the same name (without the extension) as the file corresponding to the library. For example, the <Name>.WDL library accepts the patches named <Name>.WDL.001. The <Name>.EXE executable with included WDL accepts the patches named <Name>.WDL.001. If the library or the executable does not have the same name as the project, you must modify the physical name of the patch (without changing the extension). Remark: By default, the patch history is included in the last patch made.. Only the latest patch is required. If the patch contains only the latest fixes, it is necessary to keep all patches generated alongside the executable.. All of them will be in charge of the project execution.. Limitations The following changes cannot be taken into account in a patch and require a complete update of the application: - rename a project element,
- add or delete a member of a class or structure,
- add or remove a value from an enumeration,
- add or remove an option from a combination,
- add or delete a property or procedure in an interface,
- type alias modification.
Recreating an executable When the executable (or the entire WDL) is recreated, the patches created for the previous versions are ignored. Example: | | | Creating the executable version 1 that contains the "Window1" and Window2" windows. | File name: <NomProjet>.EXE | Creating a patch 001 that corrects the "Window1" window.
When the application is run, the "Window1" window found in the patch will be taken into account. | File name: <NomProjet>.WDL.001 | Creating a patch 002 that corrects the "Window1" and "Window2" windows.
When the application is run, the "Window1" and "Window2" windows found in the patch will be taken into account. | File name: <NomProjet>.WDL.002 | Creating the executable version 2 that contains the "Window1" and Window2" windows.
This executable ignores the two previous patches. These patches can be deleted from the installation directory of the application (no automatic deletion is performed). | File name: <NomProjet>.EXE | Creating a patch 003 that corrects the "Window1" window.
When the application is run, the "Window1" window found in patch 003 will be taken into account. | File name: <NomProjet>.WDL.003 |
Patches and branches of SCM You have the ability to create patches from a branch found in the SCM. We advise you not to mix the patches performed in a branch with the ones of the main version. To apply a modification performed in the main version, this operation must be performed in the sources of the branch then the patch must be generated from the branch. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|