[dpdk-dev] [PATCH v2 3/4] Update library build process
Sergio Gonzalez Monroy
sergio.gonzalez.monroy at intel.com
Tue Oct 7 11:55:11 CEST 2014
On Mon, Oct 06, 2014 at 01:46:07PM -0700, Matthew Hall wrote:
> On Mon, Oct 06, 2014 at 11:52:34AM +0100, Sergio Gonzalez Monroy wrote:
> > Remove COMBINE_LIBS option and by default build:
> > - CONFIG_RTE_BUILD_SHARED_LIB=y : both individual and combined libraries
> > - CONFIG_RTE_BUILD_SHARED_LIB=n : single combined library
>
> As previously discussed.,It would be better for backward-compatibility of
> people linking against DPDK, if the static lib could come out as both a
> combined library and separate individual libraries by default.
>
> Otherwise everybody linking against DPDK has to change their code, and it
> won't be easy for them to move forward and backward against different DPDKs
> before and after this change.
>
> Thanks,
> Matthew.
Hi Matthew,
My understanding from previous conversations is that backward-compatibility
is not being provided for the next release, as such it is unlikely that
backward-compatibility for compile/linking will be provided.
I don't see how this particular patch would force people to change their code,
though in all likelihood they will have to as a result of ABI changes in the
following release.
The only difference now would be when they link their applications against a
single library instead of multiple separated libraries.
Thanks,
Sergio
More information about the dev
mailing list