Skip to content

Changes

Page history
Updated Build (markdown) authored by Thomas Gruber's avatar Thomas Gruber
Show whitespace changes
Inline Side-by-side
Build.md
View page @ 3243411a
......@@ -67,7 +67,7 @@ If you have no root permissions for `make install`, please set `BUILDFREQ=false`
If you want to use the Marker API in Fortran programs, LIKWID offers a native Fortran90 interface. To enable it, set `FORTRAN_INTERFACE` to `true` in `config.mk`. More information using LIKWID with Fortran look at [[Marker API with Fortran90|TutorialMarkerF90]].
# Use system Lua instead of internal Lua
By setting the variables `LUA_INCLUDE_DIR`, `LUA_LIB_DIR`, `LUA_LIB_NAME` (Lua interpreter has to use the same name, e.g. lua5.1) and `LUA_BIN` (directory of the Lua interpreter) in `config.mk`, the internal Lua library and interpreter are deactivated. The LIKWID library is linked against the provided Lua library and the Shebang of all Lua scripts is changed to the system Lua interpreter. LIKWID's Lua interface was patched to support Lua 5.1, 5.2 and 5.3. It is still recommended to use the internal Lua and only basic tests are done before a release.
By setting the variables `LUA_INCLUDE_DIR`, `LUA_LIB_DIR`, `LUA_LIB_NAME` (Lua interpreter has to use the same name, e.g. lua5.1) and `LUA_BIN` (directory of the Lua interpreter) in `config.mk`, the internal Lua library and interpreter are deactivated. The LIKWID library is linked against the provided Lua library and the Shebang of all Lua scripts is changed to the system Lua interpreter. LIKWID's Lua interface was patched to support Lua 5.1, 5.2 and 5.3. It is still recommended to use the internal Lua and only basic tests are done before a release. Lua 5.1 was not usable with LIKWID 5.0.x, fixed in 5.1.x.
# Dependencies
Although we tried to minimize the external dependencies of LIKWID, some advanced tools or only specific tool options require external packages.
......