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 BE005A00C5; Tue, 15 Feb 2022 09:55:22 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5A8A8410F3; Tue, 15 Feb 2022 09:55:22 +0100 (CET) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mails.dpdk.org (Postfix) with ESMTP id 3421140E78 for ; Tue, 15 Feb 2022 09:55:21 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 755665C024D; Tue, 15 Feb 2022 03:55:19 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 15 Feb 2022 03:55:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding: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=fm3; bh=t3+tfYHEeKuZ5/ dogtaTGuLT/ghk4w+o7mC0JqVojmM=; b=HDlIUPp8ycTf8lxBsouR0vO91YRlr1 kbLyeb01H2E2lxdcxHPp+ojXzKlftTalxIkNb2JGrPNv67sxoaZuBwhRInCAVv42 lvf7QWcI0s0bAtRX3JgYua6MXNMz+RqjooYO6G4Xqi1EI/flU8C45wokL0K810eX OtITeI57V/VMeffDokylh8Azg1vnjvRJcGbq9uf8lYUwgKEYcmwE5QCJrkZ4OXFb 08CK+P0+lBLvbxyvMywsAQX+cwOcvGbTn0taS//looCuRQqR1FRh270LCDva+7S2 BbrIWT66V69g9TqQMnHqfknvgnJ2uifN00zyvdE6kMDPo3neXrZmYjJw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date: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=fm2; bh=t3+tfYHEeKuZ5/dogtaTGuLT/ghk4w+o7mC0JqVoj mM=; b=DMevUbUti1lJWIJ/e5v2w2lj42k3vLjy70fzf96X63DHR3U5LwjAkP97r a05G892TFyFGW4W65P6EONEPNI9nXhBHi60ahc8tuprHBDZp9RIBjGYMAmqpRRkr ZO+s4PkS6spDNV8KvcvykuVasLIaPWoP/YKzduSkv5IDm6T+CTsgttfw3anbEFUU l/+u+2bJyHTN9bKcpGbuX42tqUkG6YI9vHmrkFJeMwkNu73ntijuJ/5G1EANqKy5 a+pDYbI99WS48eDMDGXW5MTQ8HxAuBmyY5ujfxtRgV6LvOipe5zdmCHuyATf64E3 NrycbJZZgqSOfvICmj7znUIzzu9IQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjeefgdduvdegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpeehfeeutedugffgjeetke eklefffeegvdejjeekjeevgeeifffgvedtlefghfegudenucffohhmrghinhepughotghu mhgvnhhtrghtihhonhdrhhhofienucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Feb 2022 03:55:18 -0500 (EST) From: Thomas Monjalon To: Tyler Retzlaff Cc: dev@dpdk.org, ocardona@microsoft.com, roretzla@microsoft.com, david.marchand@redhat.com, ferruh.yigit@intel.com, bruce.richardson@intel.com Subject: Re: out of tree driver builds broken with C++ Date: Tue, 15 Feb 2022 09:55:16 +0100 Message-ID: <4854309.a9HWlOh95j@thomas> In-Reply-To: <20220215061047.GA30066@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> References: <20220214091350.GA2793@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> <3450334.eFTFzoEnKi@thomas> <20220215061047.GA30066@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 15/02/2022 07:10, Tyler Retzlaff: > On Mon, Feb 14, 2022 at 10:22:08AM +0100, Thomas Monjalon wrote: > > 14/02/2022 10:13, Tyler Retzlaff: > > > while the driver api is "internal" we agreed some time ago that drivers > > > could be built external to the dpdk tree. by enabling the meson setup > > > option -Denable_driver_sdk=true. > > > > > > it was agreed that the driver api was internal and would attract no > > > binary compatibility support which was fine. this change has now > > > imposed a further restriction that out of tree drivers have to be > > > authored in C only as non-C++ compatible code will invariably leak into > > > the internal structures. > > > > > > you won't allow us to build C++ drivers in the dpdk tree and it seems > > > now you are preventing building of C++ drivers outside of the tree too. > > > > That's the problem of non-written assumptions, they are unknown or forgotten. > > Did we agree to support out-of-tree drivers in C++? > > > > We really need to make things clear and written in documentation. > > how / where would you prefer this be documented? I think we could add a general explanation about driver SDK in doc/guides/contributing/design.rst