From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] rte.extvars.mk: allow overriding RTE_SDK_BIN from the environment
Date: Wed, 27 Jan 2016 14:38:29 +0100 [thread overview]
Message-ID: <1907511.MEp49p1vlo@xps13> (raw)
In-Reply-To: <56A0696A.8090506@mhcomputing.net>
2016-01-20 21:15, Matthew Hall:
> On 1/20/16 7:27 AM, Thomas Monjalon wrote:
> > Hi Matthew,
> >
> > RTE_SDK_BIN is an internal variable and should not be overriden.
> >
> > Have you installed DPDK somewhere? Example:
> > make install O=mybuild DESTDIR=mylocalinstall
> >
> > Then you should build your app like this:
> > make RTE_SDK=$(readlink -e ../dpdk/mylocalinstall/usr/local/share/dpdk)
>
> Hello Thomas,
>
> Is the way the make install target really works documented somewhere?
It is poorly described here:
http://dpdk.org/doc/guides/prog_guide/dev_kit_root_make_help.html#install-targets
> This target did not exist when I first used DPDK in 2011, and since then
> I saw various documentation on building DPDK in various places, but not
> that much explanation what make install actually does. I recall various
> list threads about changing its behavior as well.
Historically, "make install" was a convenient default build (with T= option).
The DESTDIR option was added to make a real install after building.
The standard form (without T=) is now implemented to do a real install.
> For example, if I look at this apparently most official document:
>
> http://dpdk.org/doc/guides/linux_gsg/build_dpdk.html
>
> It has build examples such as:
>
> make install T=x86_64-native-linuxapp-gcc
This command finishes with this message:
Installation cannot run with T defined and DESTDIR undefined
Yes you are right, some docs are neither complete nor up-to-date.
Volunteers are welcome.
> But it does not discuss "O=" or "DESTDIR=" or any other additional
> options. From some experiments on my machine, it looks like maybe I
> could do this:
>
> make install "T=${RTE_TARGET}" "O=build" "DESTDIR=build"
>
> Is that a valid possibility, to keep it all in one easy directory?
Yes you can install where you want.
Note that this command (with T= and O=) will build in the directory $O/$T
i.e. build/${RTE_TARGET} and install in build/
Please confirm that this patch is not needed. Thanks
prev parent reply other threads:[~2016-01-27 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 5:30 Matthew Hall
2016-01-20 15:27 ` Thomas Monjalon
2016-01-21 5:15 ` Matthew Hall
2016-01-27 13:38 ` 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=1907511.MEp49p1vlo@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).