What is swipl's default DLL search path on Windows?

I am compiling an extension that depends on libgcc and libstdc++. I get
module not found errors for libgcc and libstdc++ when use_foreign_library
even though the DLLs are in the first directory of the PATH. If I compile
with -static-libgcc and -static-libstdc++ the errors go away.

I wonder if swipl controls where the DLLs are searched for or if this is
controlled by Windows?

Another observation: when using swipl-ld I must specify at least one .c or
.cc file. I can't seem to just use it to invoke the linker on .o files
only. I can work around by observing the -v output and invoke the gcc/g++
myself but it seems that one should be able to use swipl-ld for linking
only? Also if one specifies g++ to be the compiler the default linker is
still gcc. But if one specifies g++ to be the linker the compiler gets set
to be g++ as well.

Haitao
-------------- next part --------------
HTML attachment scrubbed and removed