Jan Wielemaker

May well be that the algorithm to find the home dir is disturbed at some place by the stuff that is in the build environment. See docs for the various...

--no-pce doesn't seem to be necessary as it uses `-F none`, which also disables xpce. It works for me when not creating the sate in the build tree but copying...

I see. In both cases the state includes library(ansi_term) which depends on uri_file_name/2 and thus includes library(uri) which depends on the uri.so foreign object. When started outside the Prolog source...

Pushed a commit to remove the old swipl.home and swipl.rc from the top of the source. These were old remains from the pre-cmake build setup. This makes calc in man...

As is, you cannot create a saved state using swipl-ld from the version running in the build directory because it uses `-F none`, which means that home/swipl.rc is not read...

> Is the `swipl.home` logic needed any more? I think so. It is used by the relocatable runtime environments as used for Windows and MacOS to find the home relative...

> Any suggestions about how to find out why `time` and `uri` are being included? I think they are included too early by library(ansi_term). URIs are used for smart linking...

> How would I use `swipl ... -c file.pl` to create a self-contained executable with my C code as "main"? The problem is the same as using `swipl -g ...`,...

These are related, but distinct issues IMO. Whether or not color support is desirable depends on whether the final application will talk to a console and whether or not it...

> Or put `if(current_prolog_flag(color_term,true))` around the `autoload(library(ansi_term))` in module `listing`? > And have two versions of `comment/2`? ... And we have print_message/2 calls coming from everywhere that use this stuff....