From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 887F0A052B for ; Wed, 29 Jul 2020 12:53:11 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EE66D37B7; Wed, 29 Jul 2020 12:53:10 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 5E902F04 for ; Wed, 29 Jul 2020 12:53:09 +0200 (CEST) IronPort-SDR: V4AA2OsUAmpJ6TOfYvjmSw1q6gaWDQpuSlNFA+BH2wKx404naZKT3Jr2kxFsUdLMn1uITZRW/L cGYMKoxoAylA== X-IronPort-AV: E=McAfee;i="6000,8403,9696"; a="138923568" X-IronPort-AV: E=Sophos;i="5.75,410,1589266800"; d="scan'208";a="138923568" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jul 2020 03:53:07 -0700 IronPort-SDR: Gfj060ttMqL6llDt53paur7PPvcKW4Tz+KKQ6eGfzbmIqJBcnM/kH1FT0YxjwvWO9mViBeyweV +SZo/OGDGp/Q== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,410,1589266800"; d="scan'208";a="490251420" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga006.fm.intel.com with ESMTP; 29 Jul 2020 03:53:06 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.184]) by IRSMSX104.ger.corp.intel.com ([169.254.5.236]) with mapi id 14.03.0439.000; Wed, 29 Jul 2020 11:53:05 +0100 From: "Richardson, Bruce" To: Chengchang Tang , "users@dpdk.org" CC: "linuxarm@huawei.com" , "users@dpdk.org" Thread-Topic: [dpdk-users] meson: is there a mechanism for controlling compilation configuration Thread-Index: AQHWZYNw6o94Kiu8TUqDcR7R9EOIxqkePYkw Date: Wed, 29 Jul 2020 10:53:04 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B0976FF117@IRSMSX103.ger.corp.intel.com> References: <7f4b1e45-2e82-6be9-689d-1dca24b66bff@huawei.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] meson: is there a mechanism for controlling compilation configuration X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" > -----Original Message----- > From: Chengchang Tang > Sent: Wednesday, July 29, 2020 9:36 AM > To: users@dpdk.org > Cc: linuxarm@huawei.com; users@dpdk.org; Richardson, Bruce > > Subject: Re: [dpdk-users] meson: is there a mechanism for controlling > compilation configuration >=20 > cc'ed bruce >=20 > On 2020/7/29 15:20, Chengchang Tang wrote: > > Hi, > > DPDK with 'make' will be deprecated in a future release. I have some > > questions about using meson to build DPDK. > > > > When using the make, we can change the macros in config/common_base to > > control the compiling macros. For example, if i want to debug the > > mbuf, i can set CONFIG_RTE_LIBRTE_MBUF_DEBUG=3Dy in config/common_base > > to change the compiling macros. > > > > According to my understanding. DPDK meson build dose not generate > > rte_config.h based on common_base content during compilation. Is there > > any convenient way to modify the compiling macro in meson build. If > > all the compilation macros need to be modified using environment > > variable, it is inconvenient. > > The number of build options for make was too large, so the meson build opti= ons are deliberately kept small. However, for the case of the debug build o= ptions that were previously present, this is currently a gap that is under = discussion on the DPDK dev mailing list. The discussion thread can be viewe= d in the archives, e.g. http://inbox.dpdk.org/dev/20200709134823.9176-1-l.w= ojciechow@partner.samsung.com/ . Regards, /Bruce