DPDK CI discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [dpdk-ci] [Bug 620] Request to compile mlx5 PMD in ci/iol-testing
Date: Mon, 18 Jan 2021 13:43:05 +0000	[thread overview]
Message-ID: <bug-620-149@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=620

            Bug ID: 620
           Summary: Request to compile mlx5 PMD in ci/iol-testing
           Product: lab
           Version: unspecified
          Hardware: x86
                OS: Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: job scripts
          Assignee: ci@dpdk.org
          Reporter: talshn@nvidia.com
                CC: dpdklab@iol.unh.edu
  Target Milestone: ---

Created attachment 142
  --> https://bugs.dpdk.org/attachment.cgi?id=142&action=edit
DevX SDK of 2.60

Hi,

As the mlx5 pmd is now supported on Windows OS I would like to enable the
ci/iol-testing will compile it if possible, what is missing is the DevX SDK on
the build machine.

I'm attaching the SDK installation from the 2.60 release.

You can use it or alternatively get it from
https://www.mellanox.com/products/adapter-software/ethernet/windows/winof-2

Next install the SDK in your build machine.
The SDK will expose the following new environment variables required for the
library detection in DPDK:
- variable name: DEVX_LIB_PATH will be the path to the DevX lib file
- variable name: DEVX_INC_PATH will be the path to the DevX header files

afterwards the mlx5 pmd should compile on Windows (using clang compiler).

The SDK isn't being planned to change in the near future, in case it does i'll
contact you ahead of course.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2021-01-18 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 13:43 bugzilla [this message]
2021-01-25 14:21 ` bugzilla

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=bug-620-149@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=ci@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).