I try to build a minimal relocatable build of SWI Prolog 9.0.4 on Linux, which contains only a few needed packages. I found the STATIC_EXTENSIONS switch to create only one executable, but the linking of swipl fails with following error: [ 48%] Linking C executable swipl /usr/bin/ld: libswipl.a(pl-c…

I pushed f817bbb7d3989c72a2101014338443cd14728f75 which skips all the RPATH stuff if the core is not build as a shared object. I think that is fine. Remains hard to access though. There are so many build targets and configurations that it is nearly impossible to validate all of these …

Unsure what is the problem (Ubuntu, current swipl-devel, note the new switch BUILD_TESTING=OFF): $ cmake -DSTATIC_EXTENSIONS=TRUE -DINSTALL_DOCUMENTATION=OFF -DSWIPL_SHARED_LIB=OFF -DSWIPL_STATIC_LIB=ON -DBUILD_SWIPL_LD=OFF -DSWIPL_PACKAGES_X=OFF -DBUILD_TESTING=OFF .. $ make ... [ 27%] Linking CXX…

I don’t know. It should not try to build packages/cpp anyway with -DSWIPL_PACKAGES_X=OFF. The static extensions isn’t worked out well. It is mostly there to support extensions for the WASM version. Eventually it should disable the stuff that is not compatible with it.

[image] jan: I don’t know. It should not try to build packages/cpp anyway with -DSWIPL_PACKAGES_X=OFF. Is this correct? In cmake/PackageSelection.cmake, cpp is among the list of “basic” packages (“X” only has xpce). Anyway, I can move on with cmake -DSTATIC_EXTENSIONS=TRUE -DINSTALL_DOCUMEN…

Sorry, missed the _X. Surely this cmake command must be simplified. Using -DSWIPL_PACKAGE_LIST=… is surely the way to go to get specific packages.

I think I found the way to fix the problem with the linker dependencies (Windows, static extensions), see PR 1146

[image] UweR: I think it is because of the explicit setting of set(CMAKE_INSTALL_RPATH "${SWIPL_ABS_INSTALL_ARCH_LIB}") in cmake/Install.cmake. I don’t know why it is set twice in this file. Once unconditionally and a second time if the lib path is not in the “cmake platform implicit link direct…

I don’t know if that is correct. SWIPL_SHARED_LIB / SWIPL_STATIC_LIB only has an influence to the libswipl.*, isn’t it? So the packages are still shared libraries, which need to be found by the swipl executable using RPATH. So the correct condition would be NOT STATIC_EXTENSIONS, I think. But CMAKE…

[image] UweR: I don’t know if that is correct. I think it is :slight_smile: Without libswipl.so/dylib/…, you can only use foreign extensions on ELF based systems as ELF is the only binary format that uses a process wide global dynamic symbol table to resolve the PL_* functions ((X)COFF resol…

[image] jan: So, not ELF and no shared kernel means no extensions. Just to confirm (Windows): cmake -DSWIPL_SHARED_LIB=OFF -DSWIPL_STATIC_LIB=ON .. ninja src/swipl ?- use_module(library(archive)). use_module(library(archive)). ERROR: Exported procedure archive:archive_set_header_property/2 …

[image] mgondan1: Do I understand correctly that this can’t be fixed (for the reasons stated above)? In other words, under Windows, static lib means static extensions, too. Yes. The only binary format I know about that can resolve undefined symbols against the main executable is ELF (and on…

Minimal build with STATIC_EXTENSIONS

General

Topic		Replies	Views
Static executable (-DSTATIC_EXTENSIONS) General	11	768	August 24, 2022
Where is libswipl.a? General ffi	26	2380	May 6, 2021
Are Linux static builds no longer supported by 9.3.25? Installing	5	66	July 16, 2025
Error in building with ninja Installing	6	397	January 8, 2024
Static extensions: not building General	1	270	November 24, 2022

Minimal build with STATIC_EXTENSIONS

Related topics