All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: [PATCH 0/3] real "make install" rule
Date: Fri, 26 Jul 2013 15:13:42 +0200	[thread overview]
Message-ID: <cover.1374843652.git.thomas.monjalon@6wind.com> (raw)

The current "make install" rule don't install anything.
It builds one or more targets with different configurations.

These patches allow to install only files needed to build and run a DPDK appplication.
The old behaviour is kept for compatibility and the new behaviour is
a second stage triggered by setting the DESTDIR variable.

So, the command "make install T=x86_64-default-linuxapp-gcc O=aaa DESTDIR=bbb"
will build in aaa/x86_64-default-linuxapp-gcc/ and install in bbb/.

The install directory can then be used as RTE_SDK path to build an application.

-- 
Thomas

---

Olivier Matz (3):
  mk: allow to specify O= in install rule
  mk: in install rule, don't overwrite .config if it already exists
  mk: allow to specify DESTDIR in build rule

 doc/build-sdk-quick.txt |   13 +++++++------
 mk/rte.sdkbuild.mk      |   16 ++++++++++++++++
 mk/rte.sdkinstall.mk    |   17 +++++++++--------
 3 files changed, 32 insertions(+), 14 deletions(-)

-- 
1.7.10.4

             reply	other threads:[~2013-07-26 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 13:13 Thomas Monjalon [this message]
     [not found] ` <cover.1374843652.git.thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 13:13   ` [PATCH 1/3] mk: allow to specify O= in install rule Thomas Monjalon
2013-07-26 13:13   ` [PATCH 2/3] mk: in install rule, don't overwrite .config if it already exists Thomas Monjalon
2013-07-26 13:13   ` [PATCH 3/3] mk: allow to specify DESTDIR in build rule Thomas Monjalon
2013-07-26 13:36   ` [PATCH 0/3] real "make install" rule 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=cover.1374843652.git.thomas.monjalon@6wind.com \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.