Support forum
wyDay blog
wyDay Home

Using TurboActivate & TurboFloat on Linux

TurboActivate and TurboFloat run natively on Linux (see requirements) and you can use it from any programming language. This article will show you some tips and tricks specific to Linux. You should use this article alongside one of the following:

Before you can do anything, you need to login to your LimeLM account (or sign up) and get one of the TurboActivate packages for Linux (either the dynamic library version or static library version). The packages contain examples and the library files ( or libTurboActivate.a).

"TurboActivate.dat" location

TurboActivate loads the "TurboActivate.dat" file from the same directory as the executable. If you want to load the "TurboActivate.dat" file from a directory other than the one the executable's path, then use the TA_PDetsFromPath() function.

Adding "" to your application

If you're making a C, C++, or Objective-C app then you need to make sure your application can find the "" file at runtime. We recommend including "" in the same folder as your application and compiling your app using the "rpath" linker option:


This tells your app to look in your app's directory first. Read more about using ORIGIN for a dynamic runtime library search path.

You can see the example makefiles in the "main package" for Linux to see how to use the "rpath" option when building the example app. To build the makefiles, simply pass the makefile you want to build to the "make" command. For example, to build the x86 version of the example C app, just use:

make -f makefile-x86

This will compile the Example.c file, and output the 32-bit executable (example.out) inside the same folder as the x86 (the "bin-linux/x86" folder). / dependencies

TurboActivate and TurboFloat have very few dependencies on Linux. It will work "out of the box" on x86, x64, and ARM versions of Linux. We support all of the oldest supported "LTS" (long term support) Linux releases and newer:

In short, it works on all versions of Linux released since early 2011 without any configuration.

If you're targeting older or "custom" versions of Linux, then you can use the following terminal command to get the full list of dependencies:

ldd -v