RECOMPILE GUIDE HOW TO
RECOMPILE GUIDE INSTALL
RECOMPILE GUIDE UPDATE

Most of all, Recompile excels in moment-to-moment play. Zig cc -target aarch64-macos -shared -std=c11 -O3 -fPIC -I/usr/local/lib/erlang/erts-13.0/include -L/usr/local/lib/erlang/usr/lib -undefined dynamic_lookup -flat_namespace -undefined suppress /Users/cocoa/Git/fennec_example/c_src/fennec_example.c -o /Users/cocoa/Git/fennec_example/_build/dev/lib/fennec_example/priv/nif.soĮrror(link): undefined reference to symbol '_enif_make_string'Įrror(link): first referenced in '/Users/cocoa/.cache/zig/o/a5316e27e5bd064608113ea75cd212c5/fennec_example.But that's just part of the bigger picture. Using zig on macOS will cause the build to fail. zig seems to not like the -undefined dynamic_lookup and -flat_namespace flag on macOS.Release the package to Hex.pm (make sure your release includes the correct files).

RECOMPILE GUIDE UPDATE

Update Hex package to include the checksum file. git push origin main -tagsįetch precompiled binaries from GitHub. (Optional) Test if your library can precompile to all specified targets locally. (Optional) Test if your library compiles locally. To recap, the suggested flow is the following:Īdd :fennec_precompile and relevant fennec_* options to the mix.exs. However, there is no need to track the checksum file in your version control system (git or other). It's MANDATORY to include this file in your Hex package (by updating the files field in the mix.exs). This checksum file is extremely important in the scenario where you need to release a Hex package using precompiled NIFs. In this example, the checksum file will be named as checksum-fennec_example.exs. Meanwhile, a checksum file will be generated. The example here uses macos-11 as the runner because it can generate binaries for most targets.Īfter CI has finished, you can fetch the precompiled binaries from GitHub. uses: startsWith(github.ref, 'refs/tags/')

RECOMPILE GUIDE INSTALL

uses: name: Install Erlang/OTP, Elixir and Zig github/workflows/fennec_precompile.yml name: precompile rw-r-r- 1 cocoa staff 4.5K 2 Jul 00:25 fennec_example-nif-2.16-x86_64-windows-gnu-0.1.0.tar.gzĭrwxr-xr-x 3 cocoa staff 96B 1 Jul 20:49 metadataįor this guide the workflow file is located at.

compilers ( ) fennec_base_url : ' #ĭrwxr-xr-x 11 cocoa staff 352B 1 Jul 23:17. defmodule FennecExample do use Mix.Project '0.1.0' def project do ++ Mix. Also, note that :fennec_precompile should not be added to the :compilers list. In the mix.exs file, we add :fennec_precompile to deps. You can use 'mix' to compile it, test it, and more: Your Mix project was created successfully. We start by creating a new app, say fennec_precompile.

RECOMPILE GUIDE HOW TO

In the following sections, I will walk you through how to use :fennec_precompile to precompile an example app, :fennec_example.

a working C/C++ compiler won't be a strict requirement for using your NIF app.

when a working C/C++ toolchain is not available (e.g, running livebook on some embedded devices, or running in nerves environment, where a C/C++ compiler is not included).

This is mostly useful for the following reasons: It provides a convenient way to precompile your NIF app for all the supported platforms.

:fennec_precompile aims to be a drop-in replacement for :elixir_make. Settings View Source Precompilation guide

Recompile guide