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 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 <b...@nicira.com> napsal:
>
> >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
> >> files.
> >> I think that the reason is based on inappropriate Makefile or
> >> lib/automake.mk that does not define include_HEADERS files that should be
> >> installed into ${includedir}.
> >>
> >> Would you please confirm or reject my idea? Is there any reason of current
> >> state?
> >
> >We're in the middle of a slow process of defining a public API. Until
> >then, the best bet is to either build your software as a fork of the OVS
> >repo (which is not a bad idea anyway if your ultimate goal is to get
> >OF-CONFIG support into OVS) or to build with an include path that
> >includes a full OVS source tree.
>
>
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
