Hi Ben, > I don't understand the question. These are always linked together.
I want to write a new ofproto provider and netdev provider and have them as dynamic libraries. The requirement is to have the implementation of the provider Apis contained in a separate dynamic library and not modify ovs code base by adding private patches to register providers. Hence, with this, I can download the OVS-Package, replace the dynamic library for registering providers and start using OVS without touching the OVS code base. Is the above possible today? Thanks for the response and support. Thanks, S. Aravind Prasad On Sat, Jan 20, 2018 at 2:09 AM, Ben Pfaff <[email protected]> wrote: > On Fri, Jan 19, 2018 at 10:15:46AM +0530, Aravind Prasad wrote: > > Is there a way to link OFPROTO and NETDEV libraries directly to OVS > binary > > without recompiling the OVS codebase. Like, downloading the OVS debian > > binary directly and link the ofproto and netdev dynamic libraries to it. > > I don't understand the question. These are always linked together. > > > Afaik, currently, we need to compile the OVS code with ofproto and netdev > > libraries manually. And if thats the way, is supporting multiple datapath > > elements the possible reason to mandate the recompilation of OVS codebase > > with the libraries. Just curious to know :). >
_______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
