From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A907DA0548; Thu, 2 Jun 2022 12:55:48 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3B14140691; Thu, 2 Jun 2022 12:55:48 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by mails.dpdk.org (Postfix) with ESMTP id 6FDE04021E for ; Thu, 2 Jun 2022 12:55:46 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B05015C010C; Thu, 2 Jun 2022 06:55:44 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 02 Jun 2022 06:55:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm1; t=1654167344; x= 1654253744; bh=6Vdt4brM6WjVVrB2Vip32z0jcqGLoCEdVsD+YQGzGmI=; b=s 2GE1mIAQRrOg4hdt5E0vdixhfdwfifLQ2j9MfG70VRvOO3lBE7RDACfO0HMf8I5s /n7jOgv7DKyQ5eAqWwDXBfmisfjKAcNGIHLevwZeQMXPKQhKI4huquBujeW2gOlL TBefVfSHAsJbZ9c8gQf8eVyDHVreUf/eWIzuvsJE5rmWTrneqCgJHUjDfm47ZA5L xuHHOqmc9/aX7VyC9HCV4qoPjS9HS0sc3uCLom77hSS6xZLOewePBcSh4jbtuV7C r8kIU34WxcYSKL5H84gUPHHN+jdnnsiU+xbf97EkhCU+tMgO06xj/oM1P49JCZZE +Z+KP6GLG2dL+vM+JSMvQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1654167344; x= 1654253744; bh=6Vdt4brM6WjVVrB2Vip32z0jcqGLoCEdVsD+YQGzGmI=; b=k hCfWclGlqkk0Fvpe84d1mgIvvdoorVvRNJASIdNHytXLhgNg3fXobGMyy+DsXLYQ CZ96CYYw2LTZ9JDxmOzrOu6w1dbY8TcpQoq+WD1S4vcFblt586qP8hIruC9YVuES 4MsggChZlOyjS34ePnLwtsDbw+0IY6bLy4sjk/sc/C8f7wzXcNkCiEtya3TctfVX ZGw+UhR2EUMWAi54YDlSX8BAca7Da90nkDnRUiw9IZTWakXAgnM8JXF2VgYdCdb6 fOwD78aDvThCpV0NZYijjm9q2KmeUj54M+Zcu8AymoiFurgCz4opTUNJC0TGWmk2 e4fszFaBZ0O+smLcOCk2A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrledvgdefudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvfevufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepfeehueeugfetkeeftedvhfevffdvveefkedvffeuffevfffhudet tedtvdehueehnecuffhomhgrihhnpehmvghsohhnsghuihhlugdrtghomhenucevlhhush htvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhho nhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 2 Jun 2022 06:55:41 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson , Jerin Jacob Cc: Jerin Jacob , dpdk-dev , Ruifeng Wang , Jan Viktorin , David Christensen , Konstantin Ananyev , David Marchand , Juraj =?utf-8?B?TGlua2XFoQ==?= , fengchengwen Subject: Re: [dpdk-dev] [PATCH v1] build: ccache support for cross build Date: Thu, 02 Jun 2022 12:55:36 +0200 Message-ID: <7385990.EvYhyI6sBW@thomas> In-Reply-To: References: <20220602092356.2788089-1-jerinj@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 02/06/2022 11:43, Jerin Jacob: > On Thu, Jun 2, 2022 at 3:11 PM Bruce Richardson > wrote: > > > > On Thu, Jun 02, 2022 at 02:53:55PM +0530, jerinj@marvell.com wrote: > > > From: Jerin Jacob > > > > > > By default, ccache is not used for cross build[1]. > > > Update all cross files to use ccache if it is available > > > in build machine. > > > > > > [1] > > > https://mesonbuild.com/Machine-files.html > > > > > > Signed-off-by: Jerin Jacob > > > > Does this still work even if ccache is not available? That's not fully > > Yes. > > > clear from the docs, but it seems to be that if an array is passed the > > whole array is used as the command, rather than just one element of the > > array. That would imply that cross-builds now require ccache. Is that > > acceptable? > > I have removed ccache from the build machine still it works. I don't understand why it works without ccache. In general, I would prefer we have a mechanism to update the cross file on the fly, depending on the setup. We have this for toolchain prefix name. The prefix depends on where the toochain comes from. In a "normal" build system, we set the prefix with an environment variable, not by writing a file.