Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-21 Thread Wiles, Keith
> On Jun 21, 2017, at 10:14 AM, Gaëtan Rivet wrote: > > Hi, > > On Wed, Jun 21, 2017 at 02:27:49PM +, Wiles, Keith wrote: >> >>> On Jun 21, 2017, at 5:27 AM, Bruce Richardson >>> wrote: >>> >>> On Tue, Jun 20, 2017 at 11:21:39PM +0200, Thomas Monjalon wrote: If a library or a build

Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-21 Thread Gaëtan Rivet
Hi, On Wed, Jun 21, 2017 at 02:27:49PM +, Wiles, Keith wrote: > > > On Jun 21, 2017, at 5:27 AM, Bruce Richardson > > wrote: > > > > On Tue, Jun 20, 2017 at 11:21:39PM +0200, Thomas Monjalon wrote: > >> If a library or a build tool uses a definition from a driver, > >> there is a build ord

Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-21 Thread Wiles, Keith
> On Jun 21, 2017, at 5:27 AM, Bruce Richardson > wrote: > > On Tue, Jun 20, 2017 at 11:21:39PM +0200, Thomas Monjalon wrote: >> If a library or a build tool uses a definition from a driver, >> there is a build ordering issue, like seen when moving PCI code >> into a bus driver. >> >> One opti

Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-21 Thread Richardson, Bruce
> -Original Message- > From: Thomas Monjalon [mailto:tho...@monjalon.net] > Sent: Wednesday, June 21, 2017 11:42 AM > To: Richardson, Bruce > Cc: gaetan.ri...@6wind.com; dev@dpdk.org > Subject: Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first > >

Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-21 Thread Thomas Monjalon
21/06/2017 12:27, Bruce Richardson: > On Tue, Jun 20, 2017 at 11:21:39PM +0200, Thomas Monjalon wrote: > > If a library or a build tool uses a definition from a driver, > > there is a build ordering issue, like seen when moving PCI code > > into a bus driver. > > > > One option is to keep PCI help

Re: [dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-21 Thread Bruce Richardson
On Tue, Jun 20, 2017 at 11:21:39PM +0200, Thomas Monjalon wrote: > If a library or a build tool uses a definition from a driver, > there is a build ordering issue, like seen when moving PCI code > into a bus driver. > > One option is to keep PCI helpers and some common definitions in EAL. > The ot

[dpdk-dev] [RFC PATCH] mk: symlink every headers first

2017-06-20 Thread Thomas Monjalon
If a library or a build tool uses a definition from a driver, there is a build ordering issue, like seen when moving PCI code into a bus driver. One option is to keep PCI helpers and some common definitions in EAL. The other option is to symlink every headers at the beginning of the build so they