From: Olivier MATZ <olivier.matz@6wind.com>
To: Francesco <francesco.montorsi@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Add error message when trying to use make option T= during build/clean
Date: Wed, 21 Oct 2015 21:27:20 +0200 [thread overview]
Message-ID: <5627E718.8090809@6wind.com> (raw)
In-Reply-To: <CAKW0qihdPfKdf5e4p9GoBUeGXwjFxQ=j3xLnC9F7_4zDtr529Q@mail.gmail.com>
Hi Francesco,
On 10/14/2015 10:02 AM, Francesco wrote:
> Hi Olivier,
> thanks for reviewing the patch. However for me it is logical that T=
> option is used for "config" target and then for building/cleaning only
> O= is used. However it is not logical for me that install target
> requires T= option instead of O= option... or perhaps I'm missing something?
Actually, the current behavior of install target is to build one or
several targets from templates given in the T=. To be clear, this line:
make install T=*-native-linuxapp-gcc
is equivalent to:
make config T=i686-native-linuxapp-gcc O=i686-native-linuxapp-gcc
make O=i686-native-linuxapp-gcc
make config T=x86_64-native-linuxapp-gcc O=x86_64-native-linuxapp-gcc
make O=x86_64-native-linuxapp-gcc
make config T=x86_x32-native-linuxapp-gcc O=x86_x32-native-linuxapp-gcc
make O=x86_x32-native-linuxapp-gcc
The target name "install" is probably not well chosen, and that's
probably why you are confused.
Mario is currently reworking the Makefiles to support the installation
of DPDK into a hierachical file system:
http://dpdk.org/ml/archives/dev/2015-October/024686.html
http://dpdk.org/ml/archives/dev/2015-October/025432.html
Regards,
Olivier
prev parent reply other threads:[~2015-10-21 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:04 Francesco Montorsi
2015-10-13 13:22 ` Olivier MATZ
2015-10-14 8:02 ` Francesco
2015-10-21 19:27 ` Olivier MATZ [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=5627E718.8090809@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=francesco.montorsi@gmail.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).