From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v3] mk: stop on warning only in developer build Date: Wed, 2 Mar 2016 22:04:54 +0000 Message-ID: <20160302220453.GE8804@bricha3-MOBL3> References: <9190554.3JBlDK3N1R@xps13> <1456928543-23329-1-git-send-email-thomas.monjalon@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id B921736E for ; Wed, 2 Mar 2016 23:05:18 +0100 (CET) Content-Disposition: inline In-Reply-To: <1456928543-23329-1-git-send-email-thomas.monjalon@6wind.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Mar 02, 2016 at 03:22:23PM +0100, Thomas Monjalon wrote: > From: Panu Matilainen > > Add RTE_DEVEL_BUILD make-variable which can be used to do things > differently when doing development vs building a release, > autodetected from source root .git presence and overridable via > commandline. It is used it to enable -Werror compiler flag and may > be extended to other checks. > > Failing build on warnings is a useful developer tool but its bad > for release tarballs which can and do get built with newer > compilers than what was used/available during development. Compilers > routinely add new warnings so code which built silently with cc X > might no longer do so with X+1. This doesn't make the existing code > any more buggier and failing the build in this case does not help > to improve the quality of an already released version either. > > This change the default flags which can be tuned with EXTRA_CFLAGS. > > Signed-off-by: Panu Matilainen > Signed-off-by: Thomas Monjalon Acked-by: Bruce Richardson