Compiling as a Static Library¶

Apart from building the Libtropic during your project's build process, you can build the Libtropic separately as a static library (also known as static archive on Linux) and link it later.

Compilation¶

When compiling Libtropic as a static library, a cryptography provider must always be defined, either in your CMakeLists.txt file or via the CMake command-line arguments.

To compile Libtropic as a static library on a Unix-like system, do:

$ mkdir build
$ cd build
$ cmake -DLT_CRYPTO=trezor_crypto .. # providing the crypto backend
$ make

To cross-compile Libtropic as a static library on a Unix-like system, you need a toolchain configuration file and a linker script. Both should be provided by the vendor of your platform. You can see an example of the toolchain configuration and the linker script in the libtropic-stm32 repository.

After acquiring both the toolchain configuration and the linker script, do:

$ mkdir build
$ cd build
$ cmake -DLT_CRYPTO=trezor_crypto -DCMAKE_TOOLCHAIN_FILE=<ABSOLUTE PATH>/toolchain.cmake -DLINKER_SCRIPT=<ABSOLUTE PATH>/linker_script.ld ..
$ make

Linking in a CMake Project¶

To link the compiled static library to your application, use target_link_libraries. For example:

add_executable(my_app source1.c source2.c etc.c)
target_link_libraries(my_app <absolute path to library file>)

Linking in a Make Project¶

If you are using make with a Makefile, you can include the static library by adding the following lines to your Makefile:

LDFLAGS += -L<directory where the static library file is located>
LDLIBS  += -ltropic