Process Windows Events in Loops that Take a Long Time to Run
If your code has a loop that takes a long time to run, then make sure to process Windows events by calling WindowEvent. See PureBasic WindowEvent, and PureBasic Windows Message Handling. Otherwise Windows will complain that your application has stopped responding.

My PureBasic Application Crashes on Linux when Running as an Executable, but not when Debugging in the IDE
The Chilkat PureBasic download contains one .pb file for each Chilkat class. The following code snippet exists in each .pb file.

Getting Started Instructions
Download and unzip to any directory.
The native Windows, Linux, and MacOS implementation are contained in the DLL, .so, and dylib files:
chilkatPb-9_5_0.dll (The Chilkat DLL for 64-bit Windows)
chilkatPb32-9_5_0.dll (The Chilkat DLL for 32-bit Windows)
libchilkatPb-9_5_0.dylib (The Chilkat dylib for MacOSX)
libchilkatPbM1-9_5_0.dylib (The Chilkat dylib for MacOSX M1 arm64)
libchilkatPb32-9_5_0.so (The Chilkat shared library for 32-bit Linux)
libchilkatPb-9_5_0.so (The Chilkat shared library for 64-bit Linux)
libchilkatPbArm32-9_5_0.so (The Chilkat shared library for 32-bit ARM Linux)
libchilkatPbArm64-9_5_0.so (The Chilkat shared library for 64-bit ARM Linux)
The Chilkat PureBasic modules are the .pb files beginning with "Ck". For example:
CkFtp2.pb
CkEmail.pb
CkImap.pb
CkSsh.pb
...
Important: Make sure the .pb files and .so/.dll/.dylib are from the same Chilkat version. Mixing different older/newer .pb sources with a different version shared lib will result in a crash.
Example Code: Chilkat PureBasic Module Example Code
Reference Documentation: Chilkat PureBasic Module Reference Documentation
Important: If your code using Chilkat crashes on your first try, it is because the native libary (.so, .dll, or .dylib) could not be found by the operating system. See this Chilkat Forum post for information: PureBasic OpenLibrary Failed
Note: If your PureBasic application is a shared DLL, then make sure to call each Chilkat module's ckInitGlobal before using it. For example, for CkZip call CkZip::ckInitGlobal(). The call(s) to ckInitGlobal can be placed within the AttachProcess method of the DLL.

When running your application from a compiled executable on Linux, the full path of the shared library (.so) must be specified. For example, "/home/robert/chilkatPbLib/libchilkatPb-9_5_0.so". Unfortunately, you'll need to manually update the .pb files based on the location of the shared libs. Most editors provide "Find and Replace in Files" functionality that should allow for a single find/replace for all .pb files. For example, replace "libchilkatPb" with "/home/robert/chilkatPbLib/libchilkatPb".

Only for V.I.P