The following is a step-by-step guide on how to install jluna and link it to your application. The upcoming section on troubleshooting addresses the most common errors experienced during installation.

Installing jluna#

This section will guide users on how to install jluna, either globally or in a folder-contained manner.

Cloning from Git#

First, jluna needs to be downloaded. To do this, navigate into any public folder (henceforth assumed to be Desktop) and execute:

git clone
cd jluna
mkdir build
cd build

This will have cloned the jluna git repository into the folder Desktop/jluna.

Tip: If you are using an IDE like VisualStudio, Atom, or CLion and your compilers are up-to-date, simply create a new project by cloning jluna, then have your IDE automatically configure, build, and install jluna for you. If this fails for whatever reason and you’re unable to solve it in your IDE, continue onto manual installation below instead

Configure CMake#

Before building, CMake needs to be configured. You can do so using:

# in Desktop/jluna/build

Where <compiler> is the path to one of the following compiler executables:

  • g++ (Version 10 or newer)

  • clang++ (Version 12 or newer)

  • cl (MSVC) (Version 19.32 or newer)

and <path> is the desired install path. Keep track of this path, as you may need it later.

Some errors may appear here, if this is the case, head to troubleshooting.

Make Install & Test#

Having successfully configured CMake, call:

# in Desktop/jluna/build
make install

Which will create the shared libraries, usually called on Unix and jluna.dll on Windows.

We can verify everything works by calling

# in Desktop/jluna/build
ctest --verbose

Which will produce a lot of text output. At the very end, it should say:

Number of tests unsuccessful: 0

Process finished with exit code 0

Which means jluna is working and ready to be used!


Now that jluna is installed on your system, your application can access it using:

# in users own CMakeLists.txt
find_library(jluna REQUIRED NAMES jluna)

If the above fails, you may need to manually specify, which directory jluna was installed into, using:

# in users own CMakeLists.txt
find_library(jluna REQUIRED 
    NAMES jluna
    PATHS <install path>

Where <install path> is the path specified as -DCMAKE_INSTALL_PREFIX during configuration before.

Note that jlunas install rules also export is as a package, so it will be available through find_package on systems where it was installed globally:

find_package(jluna REQUIRED)

After find_library or find_package, link your own library or executable to jluna like so:

# in your own CMakeLists.txt
target_link_libraries(<target> PRIVATE 
    "${<julia package>}"
target_include_directories(<target> PRIVATE 
    "${<jluna include directory>}" 
    "${<julia include directory>}"
target_compile_features(<target> PRIVATE cxx_std_20)


  • <target> is the identifier of your library / executable

  • <jluna include directory> is the folder containing jluna.hpp

  • <julia package> is the library/package containing the julia C-API

  • <julia include directory> is the folder containing julia.h.

The shared Julia library location is usually

  • ${JULIA_BINDIR}/../lib

while the Julia include directory is usually

  • ${JULIA_BINDIR}/../include/ or

  • ${JULIA_BINDIR}/../include/julia/

If building your library triggers linker or compiler errors, head to troubleshooting.

Example: Hello World#

A basic example main could be the following:

#include <jluna.hpp>

using namespace jluna;
int main()
    Base["println"]("hello julia");
    return 0;

Where jluna.hpp already includes julia.h.

To learn how to use more of jlunas features, continue on to the manual.