From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 01B3B683E for ; Tue, 26 Mar 2019 16:07:30 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 9653043D2; Tue, 26 Mar 2019 11:07:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 26 Mar 2019 11:07:30 -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=mesmtp; bh=d4KChQwZIaGqtE0QSUeEwYtqKAbCAKmoC8OkyrHZHOQ=; b=nweTsit7/rKk 5u0oaHxtEMCIL9egbDd3xb9tj0RMqGVbAkCs8GlhTsdP2OBb+hx5cKs1ImrBXvth aD+O0n0DVjQi/YmNM/wJylHByBPTx3ABJhpiyMwDGwZfaxl/GBWGe6la0lA/7bJc Ix2z1wDE2PG6IT5xiGHh6Sf7PVIWLFM= 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=d4KChQwZIaGqtE0QSUeEwYtqKAbCAKmoC8OkyrHZH OQ=; b=G3A3niPXTVCbDHurZsgAwh+oSvXXjdlH2ifI2E6LCwH6A6URdSCfHM999 6Shho9O5VzDz4ZHwhLAVRDKkrN7YOqRmQP13tWkKjiyXjf3RPHJlqd6quE+P/iUg uoQBZ6qhgMz9Rfqi0UwceVNiQi27Wi8IekqDnhirF1opzaxt96YiB6zRtUtr6pGC XYEbp7c6knV3wDApyuLRgSEaEaojd0l1xTsejF8sUPMaI8YF9LkYaiuwiQC6XvG1 F2oykiKUy6aRfwIOTdr5OfMgnIbCooz4WRTxgK8HjuNjnfMBF7xPyhNmBQvd3yeL 6jDJWFLsayODa9ff/xgTBMAV28NCw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkedtgdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 76537E49DE; Tue, 26 Mar 2019 11:07:27 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: Jerin Jacob Kollanukkaran , "pallavi.kadam@intel.com" , "anand.rawat@intel.com" , "dev@dpdk.org" , "ranjit.menon@intel.com" , "jeffrey.b.shaw@intel.com" Date: Tue, 26 Mar 2019 16:07:26 +0100 Message-ID: <4709724.uuJ7r4bRVe@xps> In-Reply-To: <20190326144138.GB472084@bricha3-MOBL.ger.corp.intel.com> References: <20190306041634.12976-1-anand.rawat@intel.com> <3620690.ieInrUnbAS@xps> <20190326144138.GB472084@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v5 3/8] kvargs: adding a module definition file 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: , X-List-Received-Date: Tue, 26 Mar 2019 15:07:31 -0000 26/03/2019 15:41, Bruce Richardson: > On Tue, Mar 26, 2019 at 02:55:41PM +0100, Thomas Monjalon wrote: > > 26/03/2019 14:37, Jerin Jacob Kollanukkaran: > > > On Tue, 2019-03-26 at 10:58 +0000, Bruce Richardson wrote: > > > > However, my hope is that down the road we can have the def file > > > > generated > > > > from the map file (or potentially vice versa). Perhaps the meson > > > > python > > > > module could be used to allow us to script it a bit. > > > > > > Make sense. Do we want to support shared lib for Windows for the first > > > version? or Can we live with static lib till we find a proper solution. > > > I do believe the base Windows Helloworld support needs to added this > > > release in main repo and add the subsequent features step by step. > > > I would treat, shared lib as subsequent feature if it is not clean. > > > > I agree, shared library can be supported later. > > > I would agree, except *not* supporting it will be more painful than what is > proposed here. :-) Why? We can just document it as broken, and test only "static" compilation. Am I missing something? From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 06DD7A05D3 for ; Tue, 26 Mar 2019 16:07:32 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 33DBD6904; Tue, 26 Mar 2019 16:07:32 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 01B3B683E for ; Tue, 26 Mar 2019 16:07:30 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 9653043D2; Tue, 26 Mar 2019 11:07:29 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 26 Mar 2019 11:07:30 -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=mesmtp; bh=d4KChQwZIaGqtE0QSUeEwYtqKAbCAKmoC8OkyrHZHOQ=; b=nweTsit7/rKk 5u0oaHxtEMCIL9egbDd3xb9tj0RMqGVbAkCs8GlhTsdP2OBb+hx5cKs1ImrBXvth aD+O0n0DVjQi/YmNM/wJylHByBPTx3ABJhpiyMwDGwZfaxl/GBWGe6la0lA/7bJc Ix2z1wDE2PG6IT5xiGHh6Sf7PVIWLFM= 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=d4KChQwZIaGqtE0QSUeEwYtqKAbCAKmoC8OkyrHZH OQ=; b=G3A3niPXTVCbDHurZsgAwh+oSvXXjdlH2ifI2E6LCwH6A6URdSCfHM999 6Shho9O5VzDz4ZHwhLAVRDKkrN7YOqRmQP13tWkKjiyXjf3RPHJlqd6quE+P/iUg uoQBZ6qhgMz9Rfqi0UwceVNiQi27Wi8IekqDnhirF1opzaxt96YiB6zRtUtr6pGC XYEbp7c6knV3wDApyuLRgSEaEaojd0l1xTsejF8sUPMaI8YF9LkYaiuwiQC6XvG1 F2oykiKUy6aRfwIOTdr5OfMgnIbCooz4WRTxgK8HjuNjnfMBF7xPyhNmBQvd3yeL 6jDJWFLsayODa9ff/xgTBMAV28NCw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkedtgdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 76537E49DE; Tue, 26 Mar 2019 11:07:27 -0400 (EDT) From: Thomas Monjalon To: Bruce Richardson Cc: Jerin Jacob Kollanukkaran , "pallavi.kadam@intel.com" , "anand.rawat@intel.com" , "dev@dpdk.org" , "ranjit.menon@intel.com" , "jeffrey.b.shaw@intel.com" Date: Tue, 26 Mar 2019 16:07:26 +0100 Message-ID: <4709724.uuJ7r4bRVe@xps> In-Reply-To: <20190326144138.GB472084@bricha3-MOBL.ger.corp.intel.com> References: <20190306041634.12976-1-anand.rawat@intel.com> <3620690.ieInrUnbAS@xps> <20190326144138.GB472084@bricha3-MOBL.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v5 3/8] kvargs: adding a module definition file 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" Message-ID: <20190326150726.k-1YVBwZGnlASIcpNQtXBrXoIQoZOwCJdv7E94MBV_s@z> 26/03/2019 15:41, Bruce Richardson: > On Tue, Mar 26, 2019 at 02:55:41PM +0100, Thomas Monjalon wrote: > > 26/03/2019 14:37, Jerin Jacob Kollanukkaran: > > > On Tue, 2019-03-26 at 10:58 +0000, Bruce Richardson wrote: > > > > However, my hope is that down the road we can have the def file > > > > generated > > > > from the map file (or potentially vice versa). Perhaps the meson > > > > python > > > > module could be used to allow us to script it a bit. > > > > > > Make sense. Do we want to support shared lib for Windows for the first > > > version? or Can we live with static lib till we find a proper solution. > > > I do believe the base Windows Helloworld support needs to added this > > > release in main repo and add the subsequent features step by step. > > > I would treat, shared lib as subsequent feature if it is not clean. > > > > I agree, shared library can be supported later. > > > I would agree, except *not* supporting it will be more painful than what is > proposed here. :-) Why? We can just document it as broken, and test only "static" compilation. Am I missing something?