From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 27613DE3 for ; Thu, 24 Jan 2019 10:40:04 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Jan 2019 01:40:05 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,515,1539673200"; d="scan'208";a="140898886" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.54]) by fmsmga001.fm.intel.com with SMTP; 24 Jan 2019 01:40:02 -0800 Received: by (sSMTP sendmail emulation); Thu, 24 Jan 2019 09:40:02 +0000 Date: Thu, 24 Jan 2019 09:40:01 +0000 From: Bruce Richardson To: Liron Himi Cc: "dev@dpdk.org" Message-ID: <20190124094001.GB155072@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) Subject: Re: [dpdk-dev] remove specific modules from meson/ninja build X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2019 09:40:05 -0000 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_’. > > 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