From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id D27A641DC8; Fri, 3 Mar 2023 15:12:22 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6E75B40687; Fri, 3 Mar 2023 15:12:22 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id BF93A400D6 for <dev@dpdk.org>; Fri, 3 Mar 2023 15:12:21 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 4D8BC5C00B2; Fri, 3 Mar 2023 09:12:21 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Fri, 03 Mar 2023 09:12:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type: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= 1677852741; x=1677939141; bh=7vSdti5s+8D0KqCw09rF9LutI1WU/7s2/eW n524+u4E=; b=Yn6t2FiJUdE+H9eUbYlv3XJdFsOcmHh1iuHUoKHFcp0Yln8VP8q KtUJLCYJfG8jVUDFMSW8AEbOgCngdF65zxCjjnA07Ge3dT20CANeqOlm1JzeMP+e EtgFy6ebNZYWQZssOe0EJXDZis8LmM/sWZadyAU84OtSqfLvSEa+Q+4e5X9NCvNl 5F7pLGXQPVG845wY2gHNJ+PyYFSCipL5OnBXHkD0E9VDTgqFs+0gxW3RPHqG3HZU +p2W4rcp1zE0LbWxSs3y6z+xJtTTtrc/cPeo66XLSFyR4cmn1lgLj7Ap0gR7fRV7 RFre2CENfC8nqZcCxUOE74axry0jdR+/cxw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type: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= 1677852741; x=1677939141; bh=7vSdti5s+8D0KqCw09rF9LutI1WU/7s2/eW n524+u4E=; b=d+/ZMnGB1ddDSGi8S/QZjRv7EYl+3SpiL2hCuLlLaXZknsVOqYg tAx3JBclsu6eey/Nx/rHdvGEZmuTQ7DcZWjTVc6qzGuyI4BMUgezjUgx9fU8gIb2 22IvCzRqicr54jF3szumhjHJ2vwyY2LZkxSB7ePWDExLdmJHUzXSd0A0mtLy6t6S Icein1jboQJdAX4lqK9acr8Q7FaN7gMrrCV/pbfvDf/NtRdi3i9o6h/mwOhG9Vlk i1cBREzgQcc4tWInso3Uoj+EUQMENR8GU6lWZKFbZ5W3dkd3NH5mm7D7daGTdfP6 SrZZKE2vkv98CUyoE2lZQhFhFLAKtD4zH1w== X-ME-Sender: <xms:RQACZLrga8iFw5iDlDpe_QiqXRo2251JPvl7nZGrOOKOl3jH_67XWA> <xme:RQACZFrnQwG2qpjZhYjdDQOUeqknuTiNKUtIUdXvrLpA0zZKNCNzqKBBkUbNLKB2b TBx0TjTkevCDaLEcA> X-ME-Received: <xmr:RQACZIO1HNbmN3N5omnNQtSnIG1PgtvnIoqlXqxAw3K0hdJo6pxAZBUtpXsje6Ln1By3jGK1kV3v-Lm91873knD8gw> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudelledgheeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: <xmx:RQACZO5m9ChmAv-Obm-_EGJGeDaBuTfBKxEjyDk5xMQbuy-F3snA9g> <xmx:RQACZK5rNYgTbCrDQqwoQcaiQA_TzZ1SItkwbcZJV4SVwdN0PgVC6g> <xmx:RQACZGjJy6akLogVdpHhAgDg6n_NDn2OhSNMr5sFOKZLalEninsK8A> <xmx:RQACZAn0DKyIIRX2E9nMG3nOs9-Tu2uyd34HgdUp_J3-6u_TMVM99Q> Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 Mar 2023 09:12:20 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Tyler Retzlaff <roretzla@linux.microsoft.com> Cc: dev@dpdk.org, Tal Shnaiderman <talshn@nvidia.com>, Matan Azrad <matan@nvidia.com>, Viacheslav Ovsiienko <viacheslavo@nvidia.com> Subject: Re: [PATCH v3 1/3] common/mlx5: get Windows dependency from standard variables Date: Fri, 03 Mar 2023 15:12:19 +0100 Message-ID: <6660069.gtipl9YmvM@thomas> In-Reply-To: <20230302171753.GB29061@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20230105161020.247780-1-thomas@monjalon.net> <20230302132150.3330288-2-thomas@monjalon.net> <20230302171753.GB29061@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org 02/03/2023 18:17, Tyler Retzlaff: > On Thu, Mar 02, 2023 at 02:21:48PM +0100, Thomas Monjalon wrote: > > The DevX library path had to be provided through the variables > > DEVX_INC_PATH and DEVX_LIB_PATH. > > It was non-standard and triggers some issues with recent Meson. > > is it possible for meson to search the default install location that the > devx sdk installation is normally located on windows? then only if you > installed it to some silly non-default location you have to provide > CFLAGS/LDFLAGS? Meson will look into standard system directories I guess, but DevX is never installed in a system directory. Which path do you have in mind?