[dpdk-dev] [PATCH 0/19] Separate compile time linkage between eal lib and pmd's

2014-04-12 07:04, Neil Horman: > On Thu, Apr 10, 2014 at 04:47:07PM -0400, Neil Horman wrote: > > Disconnect compile time linkage between eal library / applications and > > pmd's > > > > I noticed that, while tinkering with dpdk, building for shared libraries > > still resulted in all the test app

[dpdk-dev] [PATCH 0/19] Separate compile time linkage between eal lib and pmd's

On Tue, Apr 15, 2014 at 10:31:25AM +0200, Thomas Monjalon wrote: > 2014-04-12 07:04, Neil Horman: > > On Thu, Apr 10, 2014 at 04:47:07PM -0400, Neil Horman wrote: > > > Disconnect compile time linkage between eal library / applications and > > > pmd's > > > > > > I noticed that, while tinkering wi

[dpdk-dev] [PATCH 0/19] Separate compile time linkage between eal lib and pmd's

On Thu, Apr 10, 2014 at 04:47:07PM -0400, Neil Horman wrote: > Disconnect compile time linkage between eal library / applications and pmd's > > I noticed that, while tinkering with dpdk, building for shared libraries still > resulted in all the test applications linking to all the built pmd's, des

[dpdk-dev] [PATCH 0/19] Separate compile time linkage between eal lib and pmd's

Disconnect compile time linkage between eal library / applications and pmd's I noticed that, while tinkering with dpdk, building for shared libraries still resulted in all the test applications linking to all the built pmd's, despite not actually needing them all. We are able to tell an applicati