Deployment (Application Edition)
- Windows and Windows Mobile
With Windows and Windows Mobile depoyment method depends on whether you link SolFS statically or dynamically.
To deploy SolFS in case of dynamic linkage, just copy SolFS.dll together with your application files. No special actions are required on the end-user system. No deployment is needed in case of static linkage.
SolFS is shipped as static and dynamic library for Visual C++ and eMbedded Visual C++. 32-bit VCL units for Delphi and C++Builder link SolFS statically. 64-bit VCL units require SolFS.dll to be deployed together with your application files.
Starting with SolFS 5.2 .NET assemblies are offered in one form that does not depend on MS VC Runtime, but requires an unmanaged SolFS.dll instead. The unmanaged DLL, SolFS.dll, is provided next to SolFS5Net.dll assembly.
.NET assemblies must be deployed by copying SolFS.dll and SolFS5Net.dll from "<SolFS>\.NET" folder together with your application files.
Questions about when and how to install the assemblies to Global Assembly Cache are discussed in Working with Assemblies and the Global Assembly Cache and How to: Install an Assembly into the Global Assembly Cache articles.
You need to include eldos.solfs.jar and libjnisolfs.so as part of your application. Reference eldos.solfs.jar as the library of your project (compiler will deal with it automatically) and also put libjnisolfs.so to "lib" folder of your APK file. Then before using SolFS in your Java code you have to call System.loadLibrary("libjnisolfs");
- Linux, FreeBSD, MacOS X, iOS
The libraries are shipped as a static library and a shared object / dylib (dynamic library).
Static library is linked directly to the application. It doesn't require dynamic library to work and no specific deployment is required.
Dynamic library is provided as a file which needs to be deployed together with your application(s). No special actions are needed on the end-user system.