On Tue, Jun 20, 2017 at 05:43:56PM +0200, Timothy Redaelli wrote: > Add --enable-static-binaries configuration option for enabling or disabling > static linking with libopenvswitch, libsflow, libovsdb, libvtep, libovn and > libofproto also when --enable-shared is specified. > > This is needed to avoid link binaries with position-independent code (PIC) > that generates slower code, but to permit building the ovs shared librares, > since it's needed, for example, by the C extension wrapper for Python JSON > parsing. > > --enable-static-binaries option can only be used when both --enable-static > (default) and --enable-shared options are specified since if only > --enable-static is specified the binaries are already statically linked and if > only --enable-shared is specified the binaries cannot link with nonbuilt > static > libraries. > > Signed-off-by: Timothy Redaelli <[email protected]>
This strikes me as an unusual configuration option. Is there precedent for this in other projects? I've always taken the cost of dynamic linking as a given when a project generates shared libraries. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
