From: Bruce Richardson <bruce.richardson@intel.com>
To: Liron Himi <lironh@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] remove specific modules from meson/ninja build
Date: Thu, 24 Jan 2019 09:40:01 +0000 [thread overview]
Message-ID: <20190124094001.GB155072@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <MN2PR18MB2832212DDBD8FB1BF02A48B6C69A0@MN2PR18MB2832.namprd18.prod.outlook.com>
On Thu, Jan 24, 2019 at 06:41:01AM +0000, Liron Himi wrote:
> Hi,
>
>
> In our specific platform makefile we have removed several components.
> Some due to conflicts and some to reduce final package size.
>
> As you know this can be done by setting to ‘false’ specific
> ‘CONFIG_RTE_LIBRTE_<x>’.
>
> Is there a way to do the same in the meson/ninja process?
>
>
No, it's not possible. If we support turning on and off individual
libraries then it vastly increases the number of possible configurations
that need to be validated, and we'd need to have each library check for the
presence of it's own dependencies and behave appropriately if they are
missing. It keeps things far saner if all libraries - bar those with
specific external dependencies - are always built, and so their presence
can be relied upon by other libraries and drivers.
If you want to remove individual components I suggest you remove them at
package building time. Out of interest, are you using shared or static
libraries, and how big of space difference does omitting a few libraries
make?
/Bruce
prev parent reply other threads:[~2019-01-24 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 6:41 Liron Himi
2019-01-24 9:40 ` Bruce Richardson [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=20190124094001.GB155072@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lironh@marvell.com \
/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).