2016-06-07 08:08, Neil Horman:
> On Tue, Jun 07, 2016 at 11:34:56AM +0200, Thomas Monjalon wrote:
> > Hi Neil,
> >
> > You are creating a new directory buildtools/ which depends on mk/
> I don't know what this means. Every part of the dpdk that builds code depends
> on the infrastructure in mk/ (
Hi Neil,
You are creating a new directory buildtools/ which depends on mk/
We also have some scripts used in the build process:
scripts/auto-config-h.sh
scripts/depdirs-rule.sh
scripts/gen-build-mk.sh
scripts/gen-config-h.sh
scripts/relpath.sh
I think we sho
On Tue, Jun 07, 2016 at 11:34:56AM +0200, Thomas Monjalon wrote:
> Hi Neil,
>
> You are creating a new directory buildtools/ which depends on mk/
I don't know what this means. Every part of the dpdk that builds code depends
on the infrastructure in mk/ (save for the scripts below)
> We also have
On Tue, May 31, 2016 at 09:57:41AM -0400, Neil Horman wrote:
> Hey all-
> So heres attempt number 2 at a method for exporting PMD hardware support
> information. As we discussed previously, the consensus seems to be that pmd
> information should be:
>
> 1) Able to be interrogated on any ELF
Hey all-
So heres attempt number 2 at a method for exporting PMD hardware support
information. As we discussed previously, the consensus seems to be that pmd
information should be:
1) Able to be interrogated on any ELF binary (application binary or individual
DSO)
2) Equally functional on
5 matches
Mail list logo
