Chilkat PureBasic Module

for Windows, Linux, and Mac OS X.


v9.5.0.93 23-Nov-2022sha256: f88da270a4a9c895ccc82dc628a1419c8b5a47c8ce9d0c101fc085f168816f78
Chilkat PureBasic Module

Getting Started Instructions

  1. Download and unzip to any directory.
  2. 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)
    • (The Chilkat shared library for 32-bit Linux)
    • (The Chilkat shared library for 64-bit Linux)
    • (The Chilkat shared library for 32-bit ARM Linux)
    • (The Chilkat shared library for 64-bit ARM Linux)
  3. 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.
  4. Example Code: Chilkat PureBasic Module Example Code
  5. Reference Documentation: Chilkat PureBasic Module Reference Documentation
  6. 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
  7. 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.

Programming Tips

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.