From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: Building with 'make install T=' and 'make config T='
Date: Wed, 09 Dec 2015 18:56:21 +0100
Message-ID: <8796313.MZ6Xhbmc6L@xps13>
References: <AE83B28E-BB91-44BC-8D36-9F938E098499@intel.com>
 <3389553.DHxrbPlyKc@xps13> <93DC6E80-9DF5-4335-94D2-E45CC42C9640@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: "Wiles, Keith" <keith.wiles@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52])
 by dpdk.org (Postfix) with ESMTP id D43E0568B
 for <dev@dpdk.org>; Wed,  9 Dec 2015 18:57:37 +0100 (CET)
Received: by wmww144 with SMTP id w144so233460860wmw.1
 for <dev@dpdk.org>; Wed, 09 Dec 2015 09:57:37 -0800 (PST)
In-Reply-To: <93DC6E80-9DF5-4335-94D2-E45CC42C9640@intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2015-12-09 17:31, Wiles, Keith:
> On 12/9/15, 10:19 AM, "Thomas Monjalon" <thomas.monjalon@6wind.com> wrote:
> >Between "make config" and "make" you can modify the configuration.
> >In the next release, "make config" will be wrapped by a "configure" script
> >which will allow to configure your target in one line.
> >So we will end up with:
> >	./configure
> >	make
> >	make install
> >It may be weird to you but it is standard to others.
> 
> I understand the above configure steps and yes it is nice to have, the only problem is we do not have a real automake-autolib configuration system.
> 
> Personally I would not use automake-autolib as it requires more system resources and different version cause different problems plus M4 maybe a great language, but not very friendly. The current DPDK build system just requires make and a shell, which is very common plus very simple to install. If cross-compiling it will be harder to get all of the tools in place to support a real automake system on a embedded environment. Cross-compiling has its own problems to address.

I said "make config" will be wrapped by a "configure" script.
Does it sound like using autotools? No