Installation for C/C++¶
To install for C/C++, it is recommended that you use a pre-built package. For obfuscation purposes, in pre-built packages, a shared secret is used to decrypt providers' private keys which is obtained using encrypt_tool. This allows developers to use private keys without exposing them in the code.
Pre-built packages are available for various platforms and processor architectures upon developer request. Additional platforms will also be supported on request.
Access the releases page to download the appropriate package.
Currently, packages are available as DEB
and TGZ
packages for C/C++.
Choose the right pre-built package based on your system OS and architecture¶
Choose the appropriate package based on your system configuration: <arch>
and <abi_tag>
(e.g. scorbit_sdk-1.1.0-amd64_u20.tar.gz
):
Processor Architecture (<arch>
)¶
The SDK is built for multiple architectures. We support the following architectures:
amd64
: Intel/AMD x86_64 architecturearm64
: ARM 64-bit architecture (AARCH64)armhf
: ARM 32-bit architecture with hardware floating point (ARMv7, armhf)
ABI Tag (<abi_tag>
)¶
The ABI tag is used to specify the Application Binary Interface (ABI) compatibility. It indicates the compatibility of the package with different versions of the Scorbit SDK. The ABI tag is included in the package name and can be used to ensure that the correct version of the SDK is installed.
The following are supported ABI tags:
u12
: Ubuntu 12.04 and later, Linux systems with glibc 2.15 or lateru12dev
: Same asu12
, but built with OpenSSL built with "no-asm" option, which is useful for debugging purposesu20
: Ubuntu 20.04 and later, Linux systems with glibc 2.31 and libstdc++.6.0.28 (GLIBCXX_3.4.28) or later
More compilers and OS will be added on request.
Install C/C++ SDK on Debian/Ubuntu based systems¶
To install the C/C++ SDK on Debian/Ubuntu based systems, you can use the dpkg
command to install the pre-built .deb
package:
Installing the C/C++ SDK on Other Linux Distributions¶
To install the C/C++ SDK on Linux distributions that use Yocto, Buildroot, or other custom packaging systems, extract the pre-built .tgz
archive and manually copy the files to the appropriate directories.