DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jianshen Liu <jliu120@ucsc.edu>
To: dev@dpdk.org
Subject: Reason to alway to build both static and shared libs
Date: Wed, 3 Aug 2022 22:13:24 -0700	[thread overview]
Message-ID: <CAMgD0BrfPyd=qjrPvm_7AVGh-88f=bhZ1O4QW_BeVdXeNtQv2A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

Hi all,

Could I know the reason for always building both static and shared libs of
DPDK? I can find the patch
<https://www.mail-archive.com/dev@dpdk.org/msg83487.html> to enable this
behavior, but it seems that it didn't mention the reason behind it. Also,
if I propose a change to use "both" as the default for default_library in
meson's config file and still allow users to choose either static or shared
as they want, is there any reason against that change?

Thanks,
Jianshen

[-- Attachment #2: Type: text/html, Size: 592 bytes --]

             reply	other threads:[~2022-08-11  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  5:13 Jianshen Liu [this message]
2022-08-22 11:23 ` Bruce Richardson

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='CAMgD0BrfPyd=qjrPvm_7AVGh-88f=bhZ1O4QW_BeVdXeNtQv2A@mail.gmail.com' \
    --to=jliu120@ucsc.edu \
    --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).