From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Building with 'make install T=' and 'make config T='
Date: Wed, 09 Dec 2015 18:56:21 +0100 [thread overview]
Message-ID: <8796313.MZ6Xhbmc6L@xps13> (raw)
In-Reply-To: <93DC6E80-9DF5-4335-94D2-E45CC42C9640@intel.com>
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
prev parent reply other threads:[~2015-12-09 17:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 14:39 Wiles, Keith
2015-12-09 14:59 ` Thomas Monjalon
2015-12-09 15:32 ` Wiles, Keith
2015-12-09 16:19 ` Thomas Monjalon
2015-12-09 17:31 ` Wiles, Keith
2015-12-09 17:44 ` Wiles, Keith
2015-12-09 17:52 ` Thomas Monjalon
2015-12-13 2:03 ` [dpdk-dev] [PATCH] scripts: add help for build testing Thomas Monjalon
2015-12-14 22:04 ` Thomas Monjalon
2015-12-09 17:56 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8796313.MZ6Xhbmc6L@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).