That sounds like a good way to go for now. As the OVS API and ABI
stabilizes sufficiently, it will no longer be necessary, but it's going
to take a while.
On Fri, Jan 30, 2015 at 07:53:47AM +0100, Tomáš Čejka wrote:
> Hello Ben,
> thank you for the answer. According to your advice, we have added
Hello Ben,
thank you for the answer. According to your advice, we have added parameter
to our configure script that allows users to specify path to OVS source
codes dir.
Tomas
Dne 28. ledna 2015 17:16:56 Ben Pfaff napsal:
On Wed, Jan 28, 2015 at 03:38:37PM +0100, Tomáš Čejka wrote:
> I'm st
On Wed, Jan 28, 2015 at 03:38:37PM +0100, Tomáš Čejka wrote:
> I'm studying source codes of the OpenFlow implementation (in OVS) because of
> the OF-CONFIG project. I would like to discuss an issue that we've found.
>
> We've discovered that OVS installs static libraries without necessary header
>
Sorry for the second message, I realized I should specify my environment
more precisely...
I tested the package available at:
http://openvswitch.org/releases/openvswitch-2.3.1.tar.gz
and the older version 2.3.0.
Installation was done in standard way by ./boot.sh&&./configure
--prefix=/some/pre
Hello,
I'm studying source codes of the OpenFlow implementation (in OVS)
because of the OF-CONFIG project. I would like to discuss an issue that
we've found.
We've discovered that OVS installs static libraries without necessary
header files.
I think that the reason is based on inappropriate M
