From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [EXT] Re: [PATCH v5 3/8] kvargs: adding a module
 definition file
Date: Tue, 26 Mar 2019 14:41:38 +0000
Message-ID: <20190326144138.GB472084@bricha3-MOBL.ger.corp.intel.com>
References: <20190306041634.12976-1-anand.rawat@intel.com>
 <20190326105831.GA188340@bricha3-MOBL.ger.corp.intel.com>
 <5eeb911a2c8a3877f5ae110b88f56ba76df642de.camel@marvell.com>
 <3620690.ieInrUnbAS@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
 "pallavi.kadam@intel.com" <pallavi.kadam@intel.com>,
 "anand.rawat@intel.com" <anand.rawat@intel.com>,
 "dev@dpdk.org" <dev@dpdk.org>,
 "ranjit.menon@intel.com" <ranjit.menon@intel.com>,
 "jeffrey.b.shaw@intel.com" <jeffrey.b.shaw@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mga12.intel.com (mga12.intel.com [192.55.52.136])
 by dpdk.org (Postfix) with ESMTP id 41C9E5B1C
 for <dev@dpdk.org>; Tue, 26 Mar 2019 15:41:43 +0100 (CET)
Content-Disposition: inline
In-Reply-To: <3620690.ieInrUnbAS@xps>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

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. :-)

/Bruce