On 12/22/2013 09:15 PM, Vincent Danjean wrote: > So, all ELF library must have an SONAME that must be changed > when a NOT backward compatible change is introduced. > The minor version should be used to distinguish version > that are backward compatible.
It currently uses the libtool's --version-info, I thought it does all of this for us. Is it now wrong? The full library file name in the .icd file was there, IIRC, to be easily able to use multiple pocl's at the same time (e.g. for benchmarking reasons), but we can change that to use the symlink name if that seems to cause problems and the symlink doesn't. This is from configure.ac # The libtool library version string to use (passed to -version-info). # See: http://www.nondot.org/sabre/Mirrored/libtool-2.1a/libtool_6.html # libpocl.so should get only API additions as we are implementing a standard. # 0:0:0 == 0.6 # 1:0:0 == 0.7 (not backwards compatible with 0:0:0 due to the ICD) # 2:0:1 == 0.8 (currently backwards compatible with 0.7, thus age = 1). # 3:0:2 == 0.9 (currently backwards compatible with 0.7, thus age = 2). AC_SUBST([LIB_VERSION],["3:0:2"]) I think libtool generates the library filenames and SONAMES from this. The place where it's actually done is in lib/CL/Makefile.am: libpocl_la_LDFLAGS = -lltdl @PTHREAD_CFLAGS@ -version-info ${LIB_VERSION} -- --Pekka ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
