There are many files that a developer may want to add to a merged application. If the application is built using the Build Application Dialog in 4D, the files must be moved manually after building, or perhaps by manually executing 4D code that handles moving the files.
One of the huge advantages of using the BUILD APPLICATION command to create a merged application is that this process can be completely automated. Here is a method which demonstrates how to add a help file to a merged application, after first building the application:
| ` Method: Build_add |
` This method is specific to windows machines and 4D Runtime Volume License Light
` Instructions for making changes follow
` First built the application.
Notice that the application build project file is used to get the correct path (from the "BuildWinDestFolder" XML key).
To change this from Windows to Mac the backslash separators (\\) must all be changed to colons (:) and the XPath must be changed from:
Depending on which 4D Runtime Volume License is used and/or which type of application is being built (single-user or client-server) the location of the merged application is different. The folder that is created during the build process is named differently for each type, as follows:
4D Runtime Volume License Light Standalone Application: "Light Application\\Database\\"
4D Runtime Volume License Pro or Sponsored Standalone Application: "Final Application\\Database\\"
Client Server Application: "Client Server executable\\Server\\Server Database\\"