From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 81ED0A0AC5 for ; Thu, 2 May 2019 17:38:25 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D49E91B119; Thu, 2 May 2019 17:38:23 +0200 (CEST) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 7887E1B115 for ; Thu, 2 May 2019 17:38:22 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0FAAD25687; Thu, 2 May 2019 11:38:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 02 May 2019 11:38:22 -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=mesmtp; bh=v31sjP8s/0MDeGA2ILZMvYcgP7qTyTMzba5vF7vcpEM=; b=hKrnOgMHxsrN +MhB+lYfka1wo2VKd2bXvR8SkCwKPvG1/FE90f8wqdC011Gjl4yWap+myAnsdvjk hgjqLCJfF/mKnqKcTEXM61+zRnmhA/hinMQAA2qvIc/tFxiPW/yLuGSUBLR3/8A8 5akJfla7YWPitkPWVEWL8Bae4fZxr7w= 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=fm2; bh=v31sjP8s/0MDeGA2ILZMvYcgP7qTyTMzba5vF7vcp EM=; b=iGowYoIh/bG2Z3sdUHsIvXHYIVPrUPbqUTTzkbvkAh2fAtPZaX+fjZ6m7 h5SqvF/8JyJv+D9fXAhFBFRRdj1OfIuMjND0XQG6tEuWQ6Z4WFfpPxdHc3zGJQUR pulh5wFGa6eQsbjJka3uPLBnqpDmAReW2yelx/Du7JX4S0XymU1WAgoXzyHVTr0R kF4YvH3H75JlQdfKYQ+OQSs5JnFqp0M+C9zMu7AFPgod3GXyGRQ9yef6JGkG9KJL A0efRmdprI3vqwY8tPsCbcRIFfJlSwMq5/eFQZqT0eiQ5LWIeL6n6cJE2wUdvos0 cwUzygkjlq+51yFbl2rI8jUaqOJJA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrieelgdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 4E6DCE474A; Thu, 2 May 2019 11:38:20 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: Luca Boccassi , dev@dpdk.org Date: Thu, 02 May 2019 17:38:17 +0200 Message-ID: <7926964.KTmQl1kLhz@xps> In-Reply-To: <20190502153040.GA322@bricha3-MOBL.ger.corp.intel.com> References: <20190423220644.54589-1-bruce.richardson@intel.com> <5943797.eKmBmZ8x9O@xps> <20190502153040.GA322@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH 3/4] devtools/test-meson-builds: add testing of pkg-config file 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190502153817.W0t5mHo7SjlYNubIbyKEtiCqPOSkUUKtS_kHcctKg_M@z> 02/05/2019 17:30, Bruce Richardson: > On Thu, May 02, 2019 at 05:11:30PM +0200, Thomas Monjalon wrote: > > 02/05/2019 16:08, Luca Boccassi: > > > On Thu, 2019-05-02 at 14:17 +0100, Bruce Richardson wrote: > > > > On Thu, May 02, 2019 at 03:11:10PM +0200, Thomas Monjalon wrote: > > > > > 26/04/2019 16:56, Bruce Richardson: > > > > > > On Wed, Apr 24, 2019 at 02:37:58PM +0100, Luca Boccassi wrote: > > > > > > > On Wed, 2019-04-24 at 13:31 +0100, Bruce Richardson wrote: > > > > > > > > On Wed, Apr 24, 2019 at 12:02:24PM +0100, Luca Boccassi > > > > > > > > wrote: > > > > > > > > > On Wed, 2019-04-24 at 11:41 +0100, Bruce Richardson wrote: > > > > > > > > > > On Wed, Apr 24, 2019 at 10:22:04AM +0100, Luca Boccassi > > > > > > > > > > wrote: > > > > > > > > > > > On Tue, 2019-04-23 at 23:06 +0100, Bruce Richardson > > > > > > > > > > > wrote: > > > > > > > > > > > > +# > > > > > > > > > > > > rather > > > > > > > > > > > > than hacking our environment, just edit the .pc file > > > > > > > > > > > > prefix > > > > > > > > > > > > value > > > > > > > > > > > > +sed > > > > > > > > > > > > -i "s|prefix=|prefix=$DESTDIR|" > > > > > > > > > > > > $PKG_CONFIG_PATH/libdpdk.pc > > > > > > > > > > > > > > > > > > > > > > What about just using meson's prefix option instead? > > > > > > > > > > > Which is > > > > > > > > > > > how > > > > > > > > > > > it > > > > > > > > > > > would be used in a real use case > > > > > > > > > > > > > > > > > > > > I don't think that would fully work, as my understanding > > > > > > > > > > is that > > > > > > > > > > the > > > > > > > > > > prefix > > > > > > > > > > option would apply only to the /usr/local parts, but not > > > > > > > > > > to the > > > > > > > > > > kernel > > > > > > > > > > modules which would still try and install in /lib/. > > > > > > > > > > > > > > > > > > What about doing a meson configure -Denable_kmods=false > > > > > > > > > before the > > > > > > > > > ninja install? The modules are not needed for that test > > > > > > > > > anyway, > > > > > > > > > right? > > > > > > > > > Alternatively, the kernel src dir could be symlinked in the > > > > > > > > > build > > > > > > > > > path, > > > > > > > > > and the kernel_dir option could be used > > > > > > > > > > > > > > > > > > I'm just worried that the test should be as "realistic" as > > > > > > > > > possible, to > > > > > > > > > avoid missing something > > > > > > > > > > > > > > > > Yes, I did think of that too, but it does mean doing another > > > > > > > > configuration > > > > > > > > run in meson, and possibly a rebuild too if the > > > > > > > > rte_build_config.h > > > > > > > > file > > > > > > > > changes. Therefore I decided to use DESTDIR for the sake of > > > > > > > > speed > > > > > > > > here. I > > > > > > > > assumed there would be a pkg-config variable to adjust the > > > > > > > > output > > > > > > > > paths > > > > > > > > based on a sysroot, but couldn't find a suitable one. > > > > > > > > > > [...] > > > > > > > There actually is a pkg-config binary option, I just tried and > > > > > > > it works > > > > > > > (it seems to be disabled by default on Debian and derivatives): > > > > > > > -- > > > > > > > define-prefix > > > > > > > > > > > > > > > > > > > Any cmdline options to pkg-config don't solve the problem here as > > > > > > it means > > > > > > that the makefiles for any app need to be modified to use all > > > > > > those. > > > > > > > > > > It looks to be a good solution. > > > > > Being able to update the DPDK install directory when building > > > > > an application should be a mandatory requirement. > > > > > I suggest to wrap the call to pkg-config so we can have this > > > > > ability. > > > > > > > > > > > > > I would have expected that this issue has already been solved for > > > > packagers. I was surprised that I couldn't find an easy way to do so. > > > > > > Packagers use standard paths - so it never becomes a problem. > > > > > > If editing the file on the fly is not acceptable for the test script, > > > then I'd suggest to fall back to the pkg-config option, and just > > > document the need to use it in the docs for this scenarios. > > > > What I mean is that we should be able to compile our apps > > after using DESTDIR, not related to the test script. > > Can we use an environment variable like RTE_TARGET? DPDK_DIR? > > > We can certainly add one to our example Makefiles, it's just a couple of > lines change to each one to add a prefix to the return value from > pkg-config. I can attempt to do so in a later version of this patch, though > I'd prefer to take more time over it than we have in 19.05. > > Alternatively, we can defer the last couple of patches in this set to > 19.08, though again I'd prefer to have even this level of minimal testing > of pkg-config into 19.05. > > Let me know what you think is best? I think it's best to merge only the fixes at this stage.