From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: tools brainstorming Date: Mon, 23 Mar 2015 09:26:41 -0700 (PDT) Message-ID: <5619227.iGS6GaGv3D@xps13> References: <3571725.20GtF5MAnU@xps13> <20150320151604.GB19548@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Cc: dev-VfR2kkLFssw@public.gmane.org To: Neil Horman Return-path: In-Reply-To: <20150320151604.GB19548-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2015-03-20 11:16, Neil Horman: > On Fri, Mar 20, 2015 at 03:51:11PM +0100, Thomas Monjalon wrote: > > =09- build check with various options combinations >=20 > The kernel does this with some special make targets (make allyesconfi= g, make > randconfig, etc). They basically act as build time fuzzers and are v= ery useful. > I'm not sure that the DPDK build system is really condusive to that y= et though, > since its made up of static configuration files. This may require so= me > build environment changes Exact. Maybe that it should be thought while trying to solve the dependencies of the build configuration, =E0 la ./configure. Adding some allyesconfig and randconfig options would be great.