DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ernest Zed <kreuzerkrieg@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] DPDK port for vcpkg
Date: Wed, 27 Feb 2019 23:39:37 +0200	[thread overview]
Message-ID: <CAHK_hpJ9tABuC_vvg6ekx1SYCnd28JZqnWC7uEw0t770SAizQg@mail.gmail.com> (raw)

Hi,
I've submitted a PR <https://github.com/Microsoft/vcpkg/pull/5388> to vcpkg
<https://github.com/Microsoft/vcpkg>
vcpkg overview:
"Vcpkg helps you manage C and C++ libraries on Windows, Linux and MacOS.
This tool and ecosystem are constantly evolving; your involvement is vital
to its success!"
In short, the `port` contains CMake wrapper on top of original DPDK which
cloned from github. The `port` invokes native DPDK build system (after
checking dependencies) builds, installs and exports all necessary
libs/headers. So the end user dont have to know the internals and
prerequisites of DPDK to start using it. Once the `./vcpkg install dpdk` is
invoked your local cmake becomes aware of the new library and thats it, go
ahead, start working :)

Now, what I need is your attention to the build arguments I pass. Please
review the PR and see if any refinement is needed to build the DPDK
properly.
The CMake file which invokes the build
https://github.com/Microsoft/vcpkg/pull/5388/commits/4943d24817b6c28d8eb012923445b0200e0a2abe#diff-37ba6f3b75f1a77e6d44c8c546abaa8f

Please pay special attention to the DPDK_TARGET, DPDK_CONFIG and
DPDK_CFLAGS variables. Not sure I get everything right.

Your comments and suggestions are appreciated!

Sincerely,
Ernest

                 reply	other threads:[~2019-02-27 21:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAHK_hpJ9tABuC_vvg6ekx1SYCnd28JZqnWC7uEw0t770SAizQg@mail.gmail.com \
    --to=kreuzerkrieg@gmail.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).