From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Hall Subject: Re: [PATCH RFC] Update/Improve build system Date: Fri, 31 Oct 2014 15:33:02 -0700 Message-ID: <20141031223302.GA17415@mhcomputing.net> References: <91383E96CE459D47BCE92EFBF5CE73B004E97FFB@IRSMSX108.ger.corp.intel.com> <20141030205000.GA9956@mhcomputing.net> <91383E96CE459D47BCE92EFBF5CE73B004E9AAFB@IRSMSX108.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev-VfR2kkLFssw@public.gmane.org" To: "Gonzalez Monroy, Sergio" Return-path: Content-Disposition: inline In-Reply-To: <91383E96CE459D47BCE92EFBF5CE73B004E9AAFB-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Fri, Oct 31, 2014 at 10:45:07AM +0000, Gonzalez Monroy, Sergio wrote: > That flow work still presents some issues as they may be features that are > incompatible between each other and would need to be in different DPDK > copies. > > Regards, > Sergio So I think the two questions are: 1) Will there ever be cases where something will compile on some platform but break at runtime and thus need to be excluded from a library? 2) Are there incompatible features where the library could break if both are enabled at once? If the answer to both questions is 'No' then the simple single-shared, single-static, is definitely simplest and most reliable. Matthew.