From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 707A07DFC for ; Thu, 30 Oct 2014 21:42:08 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 20EFB80C50B; Thu, 30 Oct 2014 13:50:00 -0700 (PDT) Date: Thu, 30 Oct 2014 13:50:00 -0700 From: Matthew Hall To: "Gonzalez Monroy, Sergio" Message-ID: <20141030205000.GA9956@mhcomputing.net> References: <91383E96CE459D47BCE92EFBF5CE73B004E97FFB@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B004E97FFB@IRSMSX108.ger.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH RFC] Update/Improve build system X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Oct 2014 20:42:08 -0000 On Thu, Oct 30, 2014 at 09:18:23AM +0000, Gonzalez Monroy, Sergio wrote: > I would say that D) is a good balance, although not being the simplest. A, or D. Depending on things such as, "If you run the DPDK on Random Platform X," where X could be something like Power CPUs or other weird stuff, will all of the things needed for the Combined Lib 1) be compilable, 2) be able to load w/o errors. For example, I could see probe ctor functions from various PMD's blowing up on unsupported hardware. Like how the rte_pmd_virtio had issues when I tried it on my VM system. If we think we can make sure no platform specific stuff breaks when it ends up in Combined Lib A then A is probably the easiest for all. Matthew.