Eh, it seems we have discussed this previously already :) https://github.com/pocl/pocl/commit/5ab2b9ace0f5e666244fd9d7f37c62b828f9cf36
Pekka wrote on 2013-12-26: > 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. According to the commit log, the version number popped up initially with a patch from Vincent in https://github.com/pocl/pocl/commit/ae6c28ba2c8ad119de4ae904b5eeb529f335f628 The comment line: * Load the full soname (not the lib*.so that can be not installed because it is in the -dev package) seems to be relevant to this change, but I'm not sure I understand what is meant here. I'd prefer the pocl.icd to have just "@libdir@/libpocl.so" in it. Drop the ".VER" because: - it breaks on BSD :) - several concurrent versions of pocl is a bit of a rare use case (?) - if several versions are concurrently installed, several .icd files are needed -> user needs to edit the .icd files anyways. - I haven't seen it break without the .VER anywhere I've tried And the motivation for having the full path with "@libdir@/" is just popular demand. For multiarch packaging, it should be removed, of course. If package maintainers would prefer, this could be made to a ./configure switch, say "--enable-multiarch"? kalle ------------------------------------------------------------------------------ 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
