DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Building with 'make install T=' and 'make config T='
Date: Wed, 9 Dec 2015 14:39:11 +0000	[thread overview]
Message-ID: <AE83B28E-BB91-44BC-8D36-9F938E098499@intel.com> (raw)


I am having a problem with ‘make install T=‘ command as I was using it before. I would normally build a x86_64-native-linuxapp-gcc, clang and icc or a different config all together. Currently the ‘make install T=‘ gives a warning message at the end of the build plus creates the x86_64-native-linuxapp-XXX directory. If I use the suggested ‘make config T=‘ command this command create a directory ‘build’ with a .config file. The problem is this method does not allow me to have multiple builds at the same time.

What is the suggested method to have multiple builds without installing  into the local file system?

Regards,
Keith


             reply	other threads:[~2015-12-09 14:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 14:39 Wiles, Keith [this message]
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         ` [dpdk-dev] Building with 'make install T=' and 'make config T=' 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=AE83B28E-BB91-44BC-8D36-9F938E098499@intel.com \
    --to=keith.wiles@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).