Moving the discussion to the list instead of the bug log :) >>> Pekka Jääskeläinen just suggested to completely remove the support >>> for a standalone version. >> I disagree :) ICD is only an extension - and the overhead of dragging >> the stand-alone possibility along is small. But I think this requires >> interactive debating on IRC... > Yes, ICD being only an extension is a good point. The best would be if the > same lib worked in the both use cases.
What about having libpocl.so define the ICD versions of the calls (with POxxx prefixes) *and* standalone versions that simply call this ones? Both exported, I mean. And keeping the ICD loader as a separate library. If we did this: Scenario 1: ICD is not wanted -> install libpocl.so so that is directly loadable (in a shared library loader path (<prefix>/lib or whatever) renamed/symlinked to libOpenCL.so) Scenario 2: ICD is wanted -> install libpocl.so so that will not get loaded as libOpenCL.so (keep name or put in not loadable directory) adn install the ICD loader as libOpenCL.so.The actiual libpocl.so will be found using the /etc/xxx config files defined by ICD spec, but no one will call the "standalone" (non-prefixed) versions. Drawback is one extra indirection for every call on the standalone scenario, but I do not think it is a big deal. Carlos ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
