Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/3] Revise makefile
Date: Mon, 26 Nov 2018 16:26:03 +0900	[thread overview]
Message-ID: <1543217166-13731-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

Some of Makefiles of SPP does not work property and need to be revised.
This patches are to fix the problems. It also include changing to use
GNUmakefile instead of Makefile as in DPDK.

* It does not check dependency for compilation. If you update some of
  source codes, you need to `make clean` before `make`.

* `Makefile.spp` is used to compile DPDK with options for testing.
  However, target is remained as old `x86_64-ivshmem-linuxapp-gcc`.

Yasufumi Ogawa (3):
  makefile: fix problem of dependency is not checked
  makefile: introduce GNUmakefile
  makefile: update Makefile for testing DPDK

 GNUmakefile          | 38 ++++++++++++++++++++++++++++++++++++++
 Makefile             | 36 +-----------------------------------
 Makefile.spp         |  2 +-
 src/mirror/Makefile  |  2 +-
 src/nfv/Makefile     |  2 +-
 src/primary/Makefile |  2 +-
 src/vf/Makefile      |  2 +-
 src/vm/Makefile      |  2 +-
 8 files changed, 45 insertions(+), 41 deletions(-)
 create mode 100644 GNUmakefile

-- 
2.7.4

             reply	other threads:[~2018-11-26  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26  7:26 ogawa.yasufumi [this message]
2018-11-26  7:26 ` [spp] [PATCH 1/3] makefile: fix problem of dependency is not checked ogawa.yasufumi
2018-11-26  7:26 ` [spp] [PATCH 2/3] makefile: introduce GNUmakefile ogawa.yasufumi
2018-11-26  7:26 ` [spp] [PATCH 3/3] makefile: update Makefile for testing DPDK ogawa.yasufumi

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=1543217166-13731-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
    --to=ogawa.yasufumi@lab.ntt.co.jp \
    --cc=ferruh.yigit@intel.com \
    --cc=spp@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).