Le 12/02/2016 à 02:30 PM, Maxim Uvarov a écrit : > That needs to go to master first, than if needed back-ported to Monarch.
Ok. > > Nicolas, if you name library differently how will application know how > to link with it? 1) We provide a template makefile for all ODP apps. 2) We don't have ABI compat with multiple libs as we build for our architecture, running our own OS with no dynamic library support We could use the same name as you do, but as we don't have any Linux running underneath, it doesn't make much sense to me. BTW, why did you rename those libraries? I've been away from the ML for a while and didn't catch up the few thousands of mail I missed :) Nicolas > > I think that we can stay with fixed name for ABI compat mode and let > platforms to change it in non ABI compat mode. Assuming that generic > applications use only ABI compat .so. > > Maxim. > > On 12/02/16 15:16, Nicolas Morey-Chaisemartin wrote: >> The lib suffix "linux" (libodp-linux, libodphelper-linux) is harcoded pretty >> much everywhere in the build system. >> The goal of this series is to allow each platform to define its library >> suffix so they don't have to touch the generic files but simply the platform >> specific files. >> >> Nicolas Morey-Chaisemartin (5): >> m4: platform exports ODP_LIB_NAME >> platform: move odp-linux specific rules to linux-generic >> test: use ODP_LIB_NAME to generate libodp name >> helper: use ODP_LIB_NAME to generate libodp name >> example: use ODP_LIB_NAME to generate libodp name >> >> configure.ac | 3 +-- >> example/Makefile.inc | 2 +- >> helper/test/Makefile.am | 6 +++--- >> platform/Makefile.inc | 4 ---- >> platform/linux-generic/Makefile.am | 6 ++++++ >> platform/linux-generic/m4/configure.m4 | 6 +++++- >> test/Makefile.inc | 2 +- >> test/validation/Makefile.inc | 2 +- >> 8 files changed, 18 insertions(+), 13 deletions(-) >>
