By the way, as I already mentioned some months ago, the chicken-static
and csi-static executables produced by CMake builds on MacOS X are
always completely useless, because the are not statically linked against
libchicken.a as they should be but dynamically linked against
libchicken.dylib. This is due to the fact that CMake screws up the
linker flags -- if you want to link against a static library on MacOS X
and there exists a shared library of the same name, you have to specify
the full path to the static library file instead of using an -l flag;
otherwise the dynamic library is always preferred, even if it is
somewhere after the static one in the library search paths. I don't like
that behaviour of MacOS X, but that's the way it works. Unfortunately I
haven't found a way, yet, to convince CMake to actually behave correctly
here. Even when you specify the full library path in a
TARGET_LINK_LIBRARIES command, CMake thinks it has to be clever and turn
that into a combination of -L and -l flags.