A note about static linking: The pre-compiled static libraries for Linux, Unix and Mac OS X dependend always on a specific version of GCC or LLVM. This is due to certain versions of standard libraries, such as the libc, on which the library depends.
GCC or LLVM cannot link a library statically, if a depending library is available in a different version as the one that was used during compilation.
In this case you can only use the dynamic library, this one works always. In the download area you find an info about the GCC version that was used to compile the library.
BTW - The safest way to avoid linker errors is to compile the library on your own system . That is the reason why a DynaPDF Enterprise license was required earlier for non-Windows operating systems.
Software companies who need to port their software to another operating system are facing a huge challenge. What works on both platforms? Which parts of the software must be re-developed?
Ultimately, the goal is always to use as much existing code as possible. The larger the common code base, the lower the cost of software maintenance.
DynaPDF runs on almost all platforms and the API is always identically. The development of PDF output for multiple platforms is a breeze with DynaPDF. One problem less that you have to deal with!
Android is no longer supported. After switching from Eclipse to Android Studio the integration of native libraries is still possible but only at great expense. The integration is too complicated. Therefore, this platform had to be removed. Whether this can be changed in future depends on Google.
It is of course still possible to compile DynaPDF for this platform. However, the way to a finished application is far too long.
A pre-compiled library is available for 64 bit Itanium only. HP-UX is not often used anymore. Therefore, this version will no longer be delivered when DynaPDF 5.0 will be released.
The AIX version is available as 64 bit version for PA-RISK. The library was compiled with Visual Age and it is available as static and shared library. Since AIX has no default font directory, system fonts must be loaded with AddFontSearchPath().
No pre-compiled library is delivered for iOS but DynaPDF Enterprise contains a finish XCode project to compile the library. Since iOS supports static libraries only, a DynaPDF Enterprise license is required for this operating system.
DynaPDF for Linux is available as 32 bit and 64 bit library. Both versions are delivered as static and shared library. Since Linux has no default font directory, system fonts must be loaded with AddFontSearchPath().
DynaPDF for Mac OS X is delivered as Universal Binary for 32 bit and 64 bit Intel CPUs. The library is available as static and shared library. The libraries are compiled with LLVM. The usage on Mac OS X is almost identically in comparison to Windows. System fonts are automatically loaded. So, a very comfortable working is possible.
The Solaris version is delivered as 64 bit static and shared library for SPARC. The libraries are compiled with Solaris Studio. Since Solaris has no default font directory, system fonts must be loaded with AddFontSearchPath().
DynaPDF is developed on Windows. All Windows versions with exception of the mobile variants are of course supported (from Windows 2000 onwards). The library is delivered as 32 bit and 64 bit DLL. DynaPDF Enterprise contains also workspaces for Visual Studio 6 and 2005 to link the library statically.