Re: [ovs-dev] [PATCH 0/9] RFC: rework code base for third-party linking

2016-02-26 Thread Ben Pfaff
On Fri, Feb 26, 2016 at 03:16:07PM -0800, Ben Warren wrote: > > On Feb 26, 2016, at 2:32 PM, Ben Pfaff wrote: > > > > On Mon, Feb 22, 2016 at 03:46:50PM -0800, b...@skyportsystems.com wrote: > >> From: Ben Warren > >> > >> This patch set is a first stab at making a 'dev' distribution for > >>

Re: [ovs-dev] [PATCH 0/9] RFC: rework code base for third-party linking

2016-02-26 Thread Ben Warren
Hi Ben, > On Feb 26, 2016, at 2:32 PM, Ben Pfaff wrote: > > On Mon, Feb 22, 2016 at 03:46:50PM -0800, b...@skyportsystems.com wrote: >> From: Ben Warren >> >> This patch set is a first stab at making a 'dev' distribution for OpenVswitch >> The goal is to provide shared libraries and header file

Re: [ovs-dev] [PATCH 0/9] RFC: rework code base for third-party linking

2016-02-26 Thread Ben Pfaff
On Mon, Feb 22, 2016 at 03:46:50PM -0800, b...@skyportsystems.com wrote: > From: Ben Warren > > This patch set is a first stab at making a 'dev' distribution for OpenVswitch > The goal is to provide shared libraries and header files so that third party > applications can link in OVS rather than a

Re: [ovs-dev] [PATCH 0/9] RFC: rework code base for third-party linking

2016-02-26 Thread Ben Pfaff
On Mon, Feb 22, 2016 at 03:46:50PM -0800, b...@skyportsystems.com wrote: > - There may not seem to be much rhyme or reason as to the ordering of #include > directives in source files. My OCD pushes me towards always using a > particular > pattern, usually alphabetic with files in directories

[ovs-dev] [PATCH 0/9] RFC: rework code base for third-party linking

2016-02-22 Thread ben
From: Ben Warren This patch set is a first stab at making a 'dev' distribution for OpenVswitch The goal is to provide shared libraries and header files so that third party applications can link in OVS rather than always using the command line utilities. Design: Nothing too exotic here - some he