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 D89EEA04DB; Thu, 15 Oct 2020 15:05:45 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 757481E8C3; Thu, 15 Oct 2020 15:05:43 +0200 (CEST) Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by dpdk.org (Postfix) with ESMTP id 911061E8BF for ; Thu, 15 Oct 2020 15:05:42 +0200 (CEST) Received: by mail-wr1-f65.google.com with SMTP id e17so3341204wru.12 for ; Thu, 15 Oct 2020 06:05:42 -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=Y04nxPBsm8L0N4oM9enbTJngNlN3E13DeTioOmqeZV4=; b=J/ToIqENBYiXNpgZvoTNT6LOGMmYpxnRkyYYDtrgf1P5gV4i4nbBNVzLwZR/lKcdXl gkHTuGj4vTUpmK9Y58MmZzGKwRIMH5ZDG8W0xrZzjgQ3FnbwIufhnTAjnDA4XWUkeqJ6 leqs8i0scx6zRCimDAF6OfdOBgCGPEOzQ0Cyevw/KWRlhZnfisNHnf2w7dH0PkjQrRF0 kh/uzFDbrjDSGKfA73f4k2ghNKh2Nq8NfGUkNaWRUJZM5k25gddrVWx32isC3hhILLuz ARbDG2E8fpuWJOEbaVCahBdoYi5zmOqJAzxeVE8pwTysygkw0n2v5Zr4BSkl10sEGsNu j9Sw== X-Gm-Message-State: AOAM530QiKoIvg277zTIvQ91HIwtTNmS9AHDNPKBiZkJ2oC1BAA10iNh l+wGurfpUrKPHniJA69OvZY= X-Google-Smtp-Source: ABdhPJy8VNgF2sINWboTQCpvax74dkoqGyOTpPXqG5Ba+GC54YaHYhREPFOMLRWAO9tOmRwp15xLUw== X-Received: by 2002:adf:f810:: with SMTP id s16mr4099010wrp.424.1602767139979; Thu, 15 Oct 2020 06:05:39 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id q8sm4463091wro.32.2020.10.15.06.05.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Oct 2020 06:05:38 -0700 (PDT) Message-ID: <7dc47047bf543a0f239a1c07b3b0c67158271ba3.camel@debian.org> From: Luca Boccassi To: Bruce Richardson Cc: dev@dpdk.org, david.marchand@redhat.com, arybchenko@solarflare.com, ferruh.yigit@intel.com, thomas@monjalon.net Date: Thu, 15 Oct 2020 14:05:37 +0100 In-Reply-To: <20201015111839.GB554@bricha3-MOBL.ger.corp.intel.com> References: <20200916164429.244847-1-bruce.richardson@intel.com> <20201014141304.632120-1-bruce.richardson@intel.com> <20201014141304.632120-7-bruce.richardson@intel.com> <431a3c639870949ee8c62a6e2ab9d3a1bd567d0f.camel@debian.org> <20201015111839.GB554@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 v3 6/7] build: standardize component names and defines 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 Thu, 2020-10-15 at 12:18 +0100, Bruce Richardson wrote: > On Thu, Oct 15, 2020 at 11:30:29AM +0100, Luca Boccassi wrote: > > On Wed, 2020-10-14 at 15:13 +0100, Bruce Richardson wrote: > > > As discussed on the dpdk-dev mailing list[1], we can make some easy > > > improvements in standardizing the naming of the various components in= DPDK, > > > and their associated feature-enabled macros. > > >=20 > > > Following this patch, each library will have the name in format, > > > 'librte_.so', and the macro indicating that library is enabled = in the > > > build will have the form 'RTE_LIB_'. > > >=20 > > > Similarly, for libraries, the equivalent name formats and macros are: > > > 'librte__.so' and 'RTE__', where class is t= he > > > device type taken from the relevant driver subdirectory name, i.e. 'n= et', > > > 'crypto' etc. > > >=20 > > > To avoid too many changes at once for end applications, the old macro= names > > > will still be provided in the build in this release, but will be remo= ved > > > subsequently. > > >=20 > > > Signed-off-by: Bruce Richardson > > >=20 > > > [1] http://inbox.dpdk.org/dev/ef7c1a87-79ab-e405-4202-39b7ad6b0c71@so= larflare.com/t/#u > > > --- > > > app/test-bbdev/meson.build | 4 ++-- > > > app/test-crypto-perf/meson.build | 2 +- > > > app/test-pmd/meson.build | 12 ++++++------ > > > app/test/meson.build | 8 ++++---- > > > doc/guides/rel_notes/deprecation.rst | 8 ++++++++ > > > drivers/baseband/meson.build | 1 - > > > drivers/bus/meson.build | 1 - > > > drivers/common/meson.build | 1 - > > > drivers/common/mlx5/meson.build | 1 - > > > drivers/common/qat/meson.build | 1 - > > > drivers/compress/meson.build | 1 - > > > drivers/compress/octeontx/meson.build | 2 +- > > > drivers/crypto/meson.build | 1 - > > > drivers/crypto/null/meson.build | 2 +- > > > drivers/crypto/octeontx/meson.build | 2 +- > > > drivers/crypto/octeontx2/meson.build | 2 +- > > > drivers/crypto/scheduler/meson.build | 2 +- > > > drivers/crypto/virtio/meson.build | 2 +- > > > drivers/event/dpaa/meson.build | 2 +- > > > drivers/event/dpaa2/meson.build | 2 +- > > > drivers/event/meson.build | 1 - > > > drivers/event/octeontx/meson.build | 2 +- > > > drivers/event/octeontx2/meson.build | 2 +- > > > drivers/mempool/meson.build | 1 - > > > drivers/meson.build | 9 ++++----- > > > drivers/net/meson.build | 1 - > > > drivers/net/mlx4/meson.build | 2 +- > > > drivers/raw/ifpga/meson.build | 2 +- > > > drivers/raw/meson.build | 1 - > > > drivers/regex/meson.build | 1 - > > > drivers/vdpa/meson.build | 1 - > > > examples/bond/meson.build | 2 +- > > > examples/ethtool/meson.build | 2 +- > > > examples/ioat/meson.build | 2 +- > > > examples/l2fwd-crypto/meson.build | 2 +- > > > examples/ntb/meson.build | 2 +- > > > examples/vm_power_manager/meson.build | 6 +++--- > > > lib/librte_ethdev/meson.build | 1 - > > > lib/librte_graph/meson.build | 2 -- > > > lib/meson.build | 3 ++- > > > 40 files changed, 47 insertions(+), 55 deletions(-) > >=20 > > Does this change the share object file names too, or only the macros? > >=20 >=20 > It does indeed change the object name files, which is a little bit > concerning. However, the consensus based on the RFC seemed to be that the > benefit is likely worth the change. If we want, we can look to use symlin= ks > to the old names on install, but I think that just delays the pain since = I > would expect few to actually change their build to the new names until th= e > old ones and the symlinks completely go away. >=20 > /Bruce It is a backward incompatible change, so we need to provide symlinks, right? On upgrade, programs linked to librte_old.so will fail to start. Or was this targeted at 20.11 thus piggy-backing on the ABI change which forces a re-link? --=20 Kind regards, Luca Boccassi