Hi Mark, Mark Michelson <[email protected]> writes:
> I've once again rolled another OVN/OVS split version. It can be found > at https://github.com/putnopvut/ovn_mk2.git > > The main changes between this and the old split POC are as follows: > > * This is based on a much newer build of OVS master. Therefore, build > errors people had with dhparams.c *should* be cleared up. > > * This fixes errors with manpages.mk generation/checking, so there is > no need to do a pointless `touch` of manpages.mk during the build > process. > > * In many cases, rather than hard-coding paths to OVS, we use > variables. This isn't universally applied, but it's used for the > locations of C headers, libraries, and manpages. A logical extension of these variables might be to move to incorporate the pkgconfig files that OVS installs. We may need to generate some additional pkgconfig files for some components (maybe..) in OvS. But something like: +PKG_CHECK_MODULES([OVS], [libopenvswitch]) + in your configure.ac at OVN (with openvswitch being installed) means we get an even weaker coupling between the projects. This would give all the flags, options, etc. that are needed. I think there may be some internal headers that need to be exposed externally (moved to include/openvswitch/). Some of the common manpage includes will need to be shared (installed somewhere that they can be referenced) by the openvswitch installer. WDYT? I have started a quick mock-up. If I can spend more time next week on it I will, but can't promise anything. > Please give this a look and let me know what you think. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
