From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] reserve 'make install' for future use
Date: Fri, 6 Nov 2015 10:24:13 +0000 [thread overview]
Message-ID: <1446805454-17776-1-git-send-email-bruce.richardson@intel.com> (raw)
There has been some discussion on the list about various ways to get DPDK more
standardised in how it compiles and how it can be installed into a system as
a set of binaries.
One of the issues we face in that is that the 'make install' command is used in
DPDK to compile a copy of the SDK but not to place the resultant binaries in the
filesystem like other packages do. In order to allow us to have the option to
use 'make install' in its common meaning in a future release we need to replace
it in our packages, and allow some time for the change to a new command to bed-in.
This patchset therefore proposed to change "make install" to "make sdk" [and
"make uninstall" to "make clean-sdk"]. Using the old commands now prints out
an error message informing the user to use the new versions.
These new commands are ones that made sense to me - I'm happy enough to change
them for something else people feel is more appropriate. The key point here is
to move away from using "make install".
I would ask that if general agreement on this can be reached that such a change
be considered for 2.2, even though it is late in the day, as "freeing up" the
make install command will potentially take multiple releases as not everyone is
on the latest version, and so waiting till 2.3 to make a change will push out
any future re-use of a "make install" command by 4 months.
Regards,
/Bruce
Bruce Richardson (1):
mk: rename 'make install' to 'make sdk'
doc/guides/freebsd_gsg/build_dpdk.rst | 16 ++---
doc/guides/linux_gsg/build_dpdk.rst | 22 +++---
doc/guides/nics/intel_vf.rst | 2 +-
doc/guides/prog_guide/dev_kit_root_make_help.rst | 18 ++---
doc/guides/sample_app_ug/tep_termination.rst | 3 +-
doc/guides/sample_app_ug/vhost.rst | 3 +-
doc/guides/testpmd_app_ug/build_app.rst | 2 +-
doc/guides/xen/pkt_switch.rst | 2 +-
mk/rte.sdk.mk | 88 ++++++++++++++++++++++++
mk/rte.sdkinstall.mk | 87 -----------------------
mk/rte.sdkroot.mk | 13 +++-
scripts/gen-build-mk.sh | 2 +-
12 files changed, 133 insertions(+), 125 deletions(-)
create mode 100644 mk/rte.sdk.mk
delete mode 100644 mk/rte.sdkinstall.mk
--
2.5.0
next reply other threads:[~2015-11-06 10:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 10:24 Bruce Richardson [this message]
2015-11-06 10:24 ` [dpdk-dev] [PATCH] mk: rename 'make install' to 'make sdk' Bruce Richardson
2015-11-06 12:57 ` [dpdk-dev] [PATCH] reserve 'make install' for future use Bruce Richardson
2015-11-06 13:04 ` Thomas Monjalon
2015-11-24 16:54 ` Bruce Richardson
2015-11-25 8:48 ` Panu Matilainen
2015-11-27 17:33 ` Thomas Monjalon
2015-11-30 11:08 ` Richardson, Bruce
2015-11-30 11:27 ` Thomas Monjalon
2015-11-30 11:41 ` Richardson, Bruce
2015-11-30 11:49 ` Bruce Richardson
2015-11-30 14:26 ` Thomas Monjalon
2015-12-04 15:57 ` Thomas Monjalon
2015-12-04 16:21 ` Richardson, Bruce
2015-11-30 12:26 ` Panu Matilainen
2015-11-30 14:19 ` Thomas Monjalon
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=1446805454-17776-1-git-send-email-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).