[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dpdk-dev
Subject:    [dpdk-dev] [PATCH RFC] Update/Improve build system
From:       mhall () mhcomputing ! net (Matthew Hall)
Date:       2014-10-31 22:33:02
Message-ID: 20141031223302.GA17415 () mhcomputing ! net
[Download RAW message or body]

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.

[prev in list] [next in list] [prev in thread] [next in thread]