It's difficult to design and maintain a shared library with a stable public API and ABI. No one has done the work yet.
On Tue, Feb 10, 2015 at 07:25:47PM +0000, Papudippu, Sreedhar Reddy wrote: > Hello all, > > I have been wondering why doesn open-vswitch code links the entire > "lib/libopenvswitch.la" into every binary in the code. > > Isn't that very in-efficient? Shouldn't we create separate libraries based on > some logical divide, and then link the libraries based on the need. > > We should have created the following libraries in the source code. > 1) LACP.a. > 2) Sflow.a > 3) Vlog.a > 4) Ovsdb_client.a > 5) Etc...... > > That will give flexibility to developers who want to create their own tools > based on open-vswitch code. > > With the current design, a developer has to link almost the entire > "lib/libopenvswitch.la" even in a small tool which uses ovsdb. > > Can someone through some history behind this design. > > If there is no specific reason, can I separate these things into small > logical libraries and submit the patch? > > Regards > Sreedhar > _____________________________________________ > From: Papudippu, Sreedhar Reddy > Sent: Monday, February 09, 2015 3:10 PM > To: dev@openvswitch.org > Subject: ovsdb-idl > > > Hello all, > > I was wondering why "ovsdb-idl" client API code is not made as a separate > independent library. > > Assume if someone wants to write a new client for the ovsdb-idl, how will > he/she link the code to the source library? > How will he/she get the get the header file definitions? > > Regards > Sreedhar > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
