Original issue: https://github.com/midipix-project/slibtool/issues/7
Opened by: https://github.com/doughdemon

doughdemon commented on Nov 5, 2016

Currently, --disable-static is a no-op.

midipix commented on Nov 5, 2016

fair enough; --disable-static actually is supported at the driver level (git grep DISABLE_STATIC src/driver), however the corresponding driver flag is not being regarded anywhere.

can you confirm that within slibtool, --disable-static should mean "generarte libfoo.so but not libfoo.a, and also generate .libs/foo.lo but not .libs/foo.o"?

doughdemon commented on Nov 5, 2016

can you confirm that within slibtool, --disable-static should mean <<generarte libfoo.so but not libfoo.a, and also generate .libs/foo.lo but not .libs/foo.o>>?
I can confirm that GNU libtool does so, and don't see any reason to do something else. (Personally, I am mostly interested in libfoo.a not getting installed.)

midipix commented on Nov 5, 2016

thanks for confirming; and yes, the installation is another important aspect of that. will do.

doughdemon commented on Nov 5, 2016

Thanks!

midipix commented on Nov 5, 2016

-disable-static is now respected in compile mode (via the driver), link mode, and install mode; see commits 252629e, 1753628, and 005b656, respectively. If anything does not work as expected please let me know!

doughdemon commented on Nov 5, 2016

Seems to work well. Thanks!

doughdemon closed this on Nov 5, 2016