From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F0382C83004 for ; Wed, 29 Apr 2020 11:10:33 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 7E55B206B8 for ; Wed, 29 Apr 2020 11:10:33 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7E55B206B8 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=debian.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 34CCF1DA1B; Wed, 29 Apr 2020 13:10:32 +0200 (CEST) Received: from mail-wm1-f65.google.com (mail-wm1-f65.google.com [209.85.128.65]) by dpdk.org (Postfix) with ESMTP id 239661D9F2 for ; Wed, 29 Apr 2020 13:10:31 +0200 (CEST) Received: by mail-wm1-f65.google.com with SMTP id h4so1558644wmb.4 for ; Wed, 29 Apr 2020 04:10:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=hdRWWgda5MHrS5cmtD61uCo9JPvClw+UFSfcHCfeyas=; b=pZQgxsOOi/TVEyjCjcKqL9pAq2EZPRqaD4an3lNlFX7iKb/9iE0RH3fIEBnKLE/H11 xFJFVHvr9Y8D5MYsMOlHh0/IULRI+6R4rx6xs0keV/mfEsguJNwVYawH8HiT++4ctUJ1 dO3yUX9RpG757Xhvp/Uo6k1426KHxviLiCPWSi52YvPUGzGeyjioaq5loRoPELDTtQ/M zjQL/lxt/am6MZb0SNR44B22cwzsw9Pm1vfzZFCiEW9r6/BJ8VeBmFzzeOUjfFae4YkK a/BQyz56lbUphda6ngZPXSKX8Su+Z3JQLGDHBq89v5NTKAaOzrdrlHU2iRAhs/qolK+w k/9w== X-Gm-Message-State: AGi0PuZmaYWViig7rB583TkRpp8npdVWF0exUbkUZXqzICf3KfLW+ojw rQN5SEl0YuZwwad5bbSxWIE= X-Google-Smtp-Source: APiQypKH2wwgldGdzS3+5kCb+p+t4Vtp2+ihbff7qLOgT4DyFo6OCyzBEkd8hY0KgwRhFoxqqgszqw== X-Received: by 2002:a1c:7c10:: with SMTP id x16mr2617920wmc.74.1588158630833; Wed, 29 Apr 2020 04:10:30 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id d7sm29003875wrn.78.2020.04.29.04.10.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Apr 2020 04:10:29 -0700 (PDT) Message-ID: From: Luca Boccassi To: Bruce Richardson Cc: dev@dpdk.org, thomas@monjalon.net, david.marchand@redhat.com, ktraynor@redhat.com Date: Wed, 29 Apr 2020 12:10:29 +0100 In-Reply-To: <20200429105810.GF1907@bricha3-MOBL.ger.corp.intel.com> References: <20200429100831.398-1-bruce.richardson@intel.com> <20200429100831.398-7-bruce.richardson@intel.com> <20200429105810.GF1907@bricha3-MOBL.ger.corp.intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 6/7] build/pkg-config: improve static linking flags 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" On Wed, 2020-04-29 at 11:58 +0100, Bruce Richardson wrote: > On Wed, Apr 29, 2020 at 11:37:02AM +0100, Luca Boccassi wrote: > > On Wed, 2020-04-29 at 11:08 +0100, Bruce Richardson wrote: > > > Rather than setting -Bstatic in the linker flags when doing a static = link, > > > and then having to explicitly set -Bdynamic again afterwards, we can = update > > > the pkg-config file to use -l:libfoo.a syntax to explicitly refer to = the > > > static library in question. Since this syntax is not supported by mes= on's > > > pkg-config module directly, we can post-process the .pc files instead= to > > > adjust them. > > >=20 > > > Once done, we can simplify the examples' makefiles and the docs by re= moving > > > the explicit static flag > >=20 > > This sounds like a worthwhile feature request for Meson to me. Would > > you be up for opening an RFE on their issue tracker explaining the use > > case, please? > >=20 > Yes, I can do so. >=20 > I didn't look to implement this in meson myself because it would take so > long to get into a version that we would use as our minimum version. :-( >=20 > /Bruce Yeah that's fair, an issue to put in the radar is fine, and if anyone has time to implement it then we can remove the workarounds in the future --=20 Kind regards, Luca Boccassi