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 4A5A3A04DB; Thu, 15 Oct 2020 12:30:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 17BF61DE20; Thu, 15 Oct 2020 12:30:34 +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 7C9D81D6F9 for ; Thu, 15 Oct 2020 12:30:32 +0200 (CEST) Received: by mail-wm1-f65.google.com with SMTP id e2so3005953wme.1 for ; Thu, 15 Oct 2020 03:30:32 -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=MDIeCZcclE3J4sm0CJrUf6WogdbnOnwQOf9Zlgi2GrA=; b=YFTxjeNHC3TX7rD3tHbUMbY3s7xxPmIkuVKCRa8RZhgFBIOLeurlDgzOhjktte1zoS 2LfoGGcQj5IL1pzKwFsNaf1ln3ElYnT64HhS8WAaiqDyqX+/wyAKuzUHeV+/ykBL2+ht tjD6pq8pkMmIDJ0NafEnZJGg8jetGdeUSfT66zcs22apaBhlDk05qIiqbdeI+gF35sCU olpMnFVfne+sKP3p+uHP/22daqO6RFOHJUqklyCDB48KKkNcv7Q1z9E29bcKq3XrgcU+ XOsIcvYcew846S0Sdm+NZitObl38wgtRFypSPj0EemnhtQOqy6SWejoJlWFljM2ihPT5 nKog== X-Gm-Message-State: AOAM533PgSU4YI/ApoaFJpXbcROA0eXcqT2J1iFPNHDUP3netmkNxCOw lXfrf0R2BVAbTlunpWB6h0w= X-Google-Smtp-Source: ABdhPJzazgj8JhPZ8mNmdBMgBOOen6mBMLJKGttmDjTD0zlxAVb2zXLulIW2Z8Qexdztig3YEKpb+A== X-Received: by 2002:a1c:e045:: with SMTP id x66mr3323788wmg.104.1602757831097; Thu, 15 Oct 2020 03:30:31 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id j9sm4102688wrp.59.2020.10.15.03.30.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 15 Oct 2020 03:30:30 -0700 (PDT) Message-ID: <431a3c639870949ee8c62a6e2ab9d3a1bd567d0f.camel@debian.org> From: Luca Boccassi To: Bruce Richardson , dev@dpdk.org Cc: david.marchand@redhat.com, arybchenko@solarflare.com, ferruh.yigit@intel.com, thomas@monjalon.net Date: Thu, 15 Oct 2020 11:30:29 +0100 In-Reply-To: <20201014141304.632120-7-bruce.richardson@intel.com> References: <20200916164429.244847-1-bruce.richardson@intel.com> <20201014141304.632120-1-bruce.richardson@intel.com> <20201014141304.632120-7-bruce.richardson@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 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 DPD= K, > 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 t= he > 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 the > device type taken from the relevant driver subdirectory name, i.e. 'net', > 'crypto' etc. >=20 > To avoid too many changes at once for end applications, the old macro nam= es > will still be provided in the build in this release, but will be removed > subsequently. >=20 > Signed-off-by: Bruce Richardson >=20 > [1] http://inbox.dpdk.org/dev/ef7c1a87-79ab-e405-4202-39b7ad6b0c71@solarf= lare.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(-) Does this change the share object file names too, or only the macros? --=20 Kind regards, Luca Boccassi