Hello Wilfred!

06 Dec 20, Wilfred van Velzen wrote to Kai Richter:

 WV>>> It now states:
 WV>>> $ cmake -H. -Bbuild -DBUILD_SHARED_LIBS=OFF

 KR>> Since i had trouble to move an exsiting config to an upgraded
 KR>> system i prefer the static method for my fidonet software.

 WV> The INSTALL.md's for the different modules shouldn't conflict with
 WV> each other!

Sorry, i do agree absolutly. My intention was a pointer into a failsafe default
configuration. ;-)

For todays fidonet software i would like to see a "will continue operartion in
the future regardless what changes to the system libs will come". This would
give users the chance to operate the software even if there is noboby there who
could do modifications for a successful re-compilation.
But back to your topic.

I'm irritated about that compilation command. Within my outdated source copy
there is a huskymak.cfg as a central point for compilation configuration. All
husky modules Makefiles here do refer with include ../huskymak.cfg or other
paths. That would include $DYNLIBS that will trigger the -static compilation if
set in huskymak.cfg.

This maybe outdated because of 2012:
[...]
DYNLIBS=1
EXENAMEFLAG=-o
WARNFLAGS=-Wall
ARCH=-m32
OPTCFLAGS=-c -s -O3 -fomit-frame-pointer -fstrength-reduce -fPIC $(ARCH)
ifeq ($(DYNLIBS), 0)
  ifeq ($(OSTYPE), UNIX)
    WARNFLAGS+= -static
    OPTCFLAGS+= -static
  endif
endif
[...]

And the only cmake reference in my source is of bscmake.exe.

Regards

Kai

--- GoldED+/LNX 1.1.4.7