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 320E6A052B for ; Wed, 29 Jul 2020 13:16:29 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8443E10A3; Wed, 29 Jul 2020 13:16:28 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 44221F04 for ; Wed, 29 Jul 2020 13:16:27 +0200 (CEST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 2D0205C0131; Wed, 29 Jul 2020 07:16:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute7.internal (MEProxy); Wed, 29 Jul 2020 07:16:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=fm1; bh= 6F9Sl1TMNxPKI5NT3usbLTKMG0q6CJk0Xu+ZB1oew2s=; b=l1EG4R2PfEoXs82A j8AxHnUDeCjsH1pz1yf3TloqYrLe6VBgnImHYv2wjCfSg8yGi0qL0jmW0tQfNN0V 63HqG3ASI+c0qXT9m2rR2FQqmwg+EfTBb4jSGAMNB07wjNL+aD53jRyI6WopNYX3 FsNQBBkozX5ip29jQBFlQjJ+UxOsx6GUEh5s0vwNTI9rU7icT2h+pR61brqeCEtB FweGIFQ1sZ+nbWWoY4X/YmZght9PnnpNHhVZHY50H2ABMyj5qAJmxdT/Gn2tFVIW NbnzEVAZqoBa8SVyfLJndjRfbuW/CGr0fTEL3G86yocRu00gCTEiEu2na05h/EvU WZ9LbQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=6F9Sl1TMNxPKI5NT3usbLTKMG0q6CJk0Xu+ZB1oew 2s=; b=Brz3KZF1dxeBApw6FKxWN/l5T39Sa34ejV5CiqEIe5/lhRh0eIFbacEfp UlaM6BEglA3QY7Noqk8LxZ2v/E32GQ86RA2bGjBzfSrydWUsXFFFiiqSPtUdKMDi elaITr0p91Vnz7Bh3q0vru5kmEkeRUYZU2MgJ6VQQHixB9sFl+NQBiNOXvdJR7Op 1Jq3gmThI5hkWWy6oklDLWtg+8+7CyMTndX0JXjF36BLjoWeuYaN5JMDzOG6mcMs 8z7jt7Zms0zIfTSvkogyZpF1SEH/jkLHRF3Bqha0/dbOeuzV/ARQnZBjtgMwMhrB chgonC+g349wsWonmMT23NTBZ2wag== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrieeggdefkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeffvdffjeeuteelfeeileduudeugfetjeelveefkeejfeeigeehteff vdekfeegudenucffohhmrghinhepughpughkrdhorhhgnecukfhppeejjedrudefgedrvd dtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B182F3060067; Wed, 29 Jul 2020 07:16:22 -0400 (EDT) From: Thomas Monjalon To: Chengchang Tang Cc: linuxarm@huawei.com, users@dpdk.org, Lukasz Wojciechowski Date: Wed, 29 Jul 2020 13:16:20 +0200 Message-ID: <7437000.11AanSTI0A@thomas> In-Reply-To: <7f4b1e45-2e82-6be9-689d-1dca24b66bff@huawei.com> References: <7f4b1e45-2e82-6be9-689d-1dca24b66bff@huawei.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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" 29/07/2020 09:20, Chengchang Tang: > 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=y 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. Please look at the work done in this series: https://patches.dpdk.org/project/dpdk/list/?series=10930&state=*