diff options
author | Sverker Eriksson <sverker@erlang.org> | 2022-01-13 21:50:44 +0100 |
---|---|---|
committer | Sverker Eriksson <sverker@erlang.org> | 2022-01-13 21:50:44 +0100 |
commit | 493472016bde97de510bfedb8f6557bc371d0066 (patch) | |
tree | eb51711ce35a1979581f4f153f518949012a7e12 /HOWTO | |
parent | ed0f6ef0144d18406b035f9cc964bfb36d166ab7 (diff) | |
parent | 27775b501f272f69af2e40809a2c83a0bc25a722 (diff) | |
download | erlang-493472016bde97de510bfedb8f6557bc371d0066.tar.gz |
Merge branch 'sverker/static-nif-init' OTP-17729
Diffstat (limited to 'HOWTO')
-rw-r--r-- | HOWTO/INSTALL.md | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/HOWTO/INSTALL.md b/HOWTO/INSTALL.md index dd06828e91..2b983497f0 100644 --- a/HOWTO/INSTALL.md +++ b/HOWTO/INSTALL.md @@ -396,11 +396,10 @@ Some of the available `configure` options are: that do not support dynamic linking of libraries it is possible to statically link nifs and drivers with the main Erlang VM binary. This is done by passing a comma separated list to the archives that you want to statically link. e.g. - `--enable-static-nifs=/home/$USER/my_nif.a`. The path has to be absolute and the - name of the archive has to be the same as the module, i.e. `my_nif` in the - example above. This is also true for drivers, but then it is the driver name - that has to be the same as the filename. You also have to define - `STATIC_ERLANG_{NIF,DRIVER}` when compiling the .o files for the nif/driver. + `--enable-static-nifs=/home/$USER/my_nif.a`. The paths have to be absolute. + For drivers, the driver name has to be the same as the filename. You also + have to define `STATIC_ERLANG_NIF_LIBNAME` (see `erl_nif` documentation) or + `STATIC_ERLANG_DRIVER` when compiling the .o files for the nif/driver. If your nif/driver depends on some other dynamic library, you now have to link that to the Erlang VM binary. This is easily achieved by passing `LIBS=-llibname` to configure. |