User Mode API

Windows: Note: The user-mode API must be deployed to end-user systems together with the kernel-mode drivers; the version of the kernel-mode drivers on the end-user systems must be equal or newer to the version of the user-mode APIs. Thus, when the user-mode API is installed or updated on end-user systems, it is required to ensure that the kernel-mode drivers already present in the system are updated to match the version of the installed user-mode API. The user mode API comes in one or two forms depending on the platform:

    • Windows: As dynamic libraries with import libraries, named cbfsstorage20.dll and cbfsstorage20.lib, respectively (available for x64 and x86 processor architectures)
    • Linux: As dynamic libraries, named libcbfsstorage.so.20.0 (available for x64 and x86 processor architectures)
    • macOS: As dynamic libraries, named libcbfsstorage20.0.dylib (available for x64 and ARM64 processor architectures)
    • Windows: As static libraries, which don't require a dynamic library, named cbfsstorage20s.lib.
    • iOS: As a static library, which doesn't require a dynamic library, named cbfsstorage20.0.a.

Windows:

Use the DLL with the import library if incompatibilities occur between the compilation and linkage options set in your project and the options with which the library was compiled.

When linking the static library, no extra user mode API files need to be deployed with the application. When using the DLL, deploy the .dll file to the target system and place it next to the application's .exe file.

Note: When linking the static library, the Windows library version.lib must be included in the linker options.

Windows Only: Remember to deploy the drivers too, as they are an integral part of CBFS Storage.

Copyright (c) 2021 Callback Technologies, Inc. - All rights reserved.
CBFS Storage 2020 C++ Edition - Version 20.0 [Build 8031]