Documentation | Deploying
By default, TatukGIS contains all general-purpose layers and functionality built-in. That means it is not required to deploy any other library, and a DK developed application is self-contained.
It is sometimes required to deliver 3rd party libraries, like ECW, MrSID. SQLITE, etc.
On the Windows operating system, libraries can exist in 32bit and 64bit versions. As long as the application runs only in 32- or in 64- bits mode, libraries can be simply deployed to the same folder as an application.
Things are a bit more complicated if the application is deployed as 32-bit and with 64-bit enabled (e.g. .NET app). Then libraries should be placed in an
x64/ subfolders. Then an application uses the proper version of the library depending on the mode of execution. Those folders can also be used in Delphi apps. For example, the TatukGIS Editor/Viewer has two executables: one for 32-bit and one 64-bit application. Both are deployed to a single folder with,
x64/ subfolders for 3rd party libraries.
Deployment libraries are located in an installation folder of the DK in a Deployment subfolder-folder. Some libraries (e.g. ECW, MrSID) require that developer that a developer will download libraries from the vendor on his own. Please, refer to readme file located in a particular library folder.
Be aware that some 3rd party libraries require a specific version of Microsoft Visual C++ Redistributable Package and the application setup procedure should ensure that a proper version is installed.
Generally, all datums, projections etc., are included in the library. However, sometimes local grid shift files are required. Due to size, these files must be deployed individually.
Grid shift files, if required. should all be deployed to
Datums subfolder (see also Grid Shifts Files).
The final application folder structure can be similar to:
+--app | +-- x86 | +-- x64 | +-- Datums