DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ibtisam Tariq <ibtisam.tariq@emumba.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-users] Difference in make exec-env: linuxapp and linux
Date: Tue, 28 Jul 2020 21:07:57 +0500	[thread overview]
Message-ID: <CA+8bGBuyznC0Yf9KzYuh5qRZEzr_Ek5DV1cj48aeW=Qb7fe37w@mail.gmail.com> (raw)
In-Reply-To: <20200728103147.GB2333@bricha3-MOBL.ger.corp.intel.com>

Ok, thanks for the clarification.

On Tue, Jul 28, 2020 at 3:31 PM Bruce Richardson <bruce.richardson@intel.com>
wrote:

> On Tue, Jul 28, 2020 at 03:23:48PM +0500, Ibtisam Tariq wrote:
> > Hello.
> >
> > We have several targets in dpdk/config when compiling using MAKE. The
> > dpdk target format is ARCH-MACHINE-EXECENV-TOOLCHAIN where EXECENV can
> > be linux, linuxapp, freebsd and bsdapp. What is the difference between
> > linuxapp and linux?
> >
> > It seems the same because they both have the same .config files.
> >
> They are indeed the same, they are just aliases for the same config files.
>
> Please note though, that from DPDK 20.11 release onwards, the Make build
> system will be removed from DPDK, and you should use meson and ninja
> instead to build DPDK, and thereafter use the libdpdk.pc pkg-config file to
> compile and link applications against the DPDK instance.
>
> Regards,
> /Bruce
>


-- 
- Ibtisam

      reply	other threads:[~2020-07-28 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 10:23 Ibtisam Tariq
2020-07-28 10:31 ` Bruce Richardson
2020-07-28 16:07   ` Ibtisam Tariq [this message]

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='CA+8bGBuyznC0Yf9KzYuh5qRZEzr_Ek5DV1cj48aeW=Qb7fe37w@mail.gmail.com' \
    --to=ibtisam.tariq@emumba.com \
    --cc=bruce.richardson@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).