From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id BAC9FA054F; Tue, 16 Mar 2021 10:59:30 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8C64C2428D7; Tue, 16 Mar 2021 10:59:30 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id C3E4B4069F for ; Tue, 16 Mar 2021 10:59:28 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 4AF355C00F4; Tue, 16 Mar 2021 05:59:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 16 Mar 2021 05:59:28 -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=fm3; bh= BXzejmZZ4+iG1UyGURkeQgsACF0+nTEixNRevFzZwz0=; b=r6PYKv+tKF2zVhKA zE5r+L9CHlOonmlAWR71Z+jblszBVCCn3OwXOl6SYiQiu9Ni8iv3npb8PyWMMXUy ihZOVSV89uQ+0VNql/h7+cU/pqtOj4rPEhhjyMQifLBxUqZNak+30HTy3FNlG1z9 Q2WaM98ee5XcklPJEzSP3PSpHlT6uArFHjjCg0wTMHlW/t5rMhwhYD3wj366ssY3 IZToZb8G20882EjOLBe/FY0WDtYmV0dbNcEFkHpOKfETRKVN2Oj+RZC1IRWgWz0W gMKbS2TbjV9NqK1JEA288b7oJrwuTUE+pg4r6QLlQXKp3HDoP5wQbGgfZ8+025gi 0IC+Xw== 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=BXzejmZZ4+iG1UyGURkeQgsACF0+nTEixNRevFzZw z0=; b=raEvBG5+lsPaBD22KFlSXsErJbLX1biflQLSfy9KNjvxQS6RayiFhXGhf eEvw9TeSZiDnNw9I+mlFOk3x6K7DvTkXBlq6PBr6KYnDy5RH7cR0Qa9VtwzdBnGI j7rdLk6y1yqItdrmTi0DT1WsCjYAoE8tWFSrcFST9QTvAQu55CkyxGyF8HNsSpMe 04D8qkEAU/WMAd/vrUhKpEsooybQ/OfxATGZmvvCJIm0VHC1/xAhemwVK4Ps0HZ0 NJnnTYp7WsCbCsUtVGXXJt7X7vs0HaiiIett/9OLdH7b/AJGS9oXUBmybwx3asx6 Fy2u+zso/k379VXUagPSNFco/QzwA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudefvddgtdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepudeggfdvfeduffdtfeeglefghfeukefgfffhueejtdetuedtjeeu ieeivdffgeehnecukfhppeejjedrudefgedrvddtfedrudekgeenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghl ohhnrdhnvght 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 32B911080063; Tue, 16 Mar 2021 05:59:27 -0400 (EDT) From: Thomas Monjalon To: Dmitry Kozlyuk Cc: dev@dpdk.org, Nick Connolly , Khoa To , Bruce Richardson Date: Tue, 16 Mar 2021 10:59:26 +0100 Message-ID: <2135687.kELr9COJfQ@thomas> In-Reply-To: <20210306000500.8698-4-dmitry.kozliuk@gmail.com> References: <20210221142819.6769-1-dmitry.kozliuk@gmail.com> <20210306000500.8698-1-dmitry.kozliuk@gmail.com> <20210306000500.8698-4-dmitry.kozliuk@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4 3/4] build: indicate usage at build time for public headers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 06/03/2021 01:04, Dmitry Kozlyuk: > DPDK code often relies on functions that are not standard C, > but are found on all platforms, even if by slightly different names. > Some headers provide macros or inline difinitions for such symbols. > However, when placed in public headers, these symbols are unnecessarily > exposed to DPDK consumers. > > Define RTE_BUILD_INTERNAL at build time. > In its presense public headers can provide additional definitions > for internal code, but hide them from external consumers. Is there a way to split public and internal headers, and avoid playing with RTE_BUILD_INTERNAL?