Hi Jan, Чт 30 апр 2020 @ 14:40 Jan Wielemaker <j.wielema...@vu.nl>:
> In theory we could have a package that merely contains /usr/bin/swipl > and /usr/lib/libswipl.so.8.2.0. That is enough to run saved states > (provided they have been built such that no dependencies need to be > loaded at runtime) and is indeed a lot smaller than swi-prolog-nox. > Possibly bundle these two as swi-prolog-runtime and make swi-prolog-nox > depend on it? > > A small problem is that running `swipl` will result in a big ugly error > message that it cannot find its startup resources. One could add > boot.prc to the runtime package which would allow running Prolog (but > without any library). > > I'm pretty neutral in this. Eye is for the time being the only > use case, but who knows there will be more :) Recently I was (again!) approached by some embedded developers who asked to provide Core_system as a separate package and try to break swi-prolog-nox into several smaller packages. Currently, I'm thinking about breaking it into swi-prolog-core (containing Core_system), swi-prolog-core-packages (containing Core_packagse; depends on swi-prolog-core) and swi-prolog-nox (containing other components from the original swi-prolog-nox; depends on swi-prolog-core and swi-prolog-core-packages). What do you think about it? Cheers! Lev
