On 09/17/2012 12:51 PM, Vincent Danjean wrote: > Do you really want to complicate linkage when using external projects ? > I recall that neither Intel, nor AMD, nor NVidia provide a standalone > libOpenCL.so. All of them provide only an ICD. They also provide each > an ICD Loader as libOpenCL.so, but these libOpenCL.so can be used to load > any ICD. > > I wont insist any more on that part because I'm also upstream for > ocl-icd (so my mail can be seen as "please, use my software"). I just > want you should carefully measure advantage/inconvenient between adding an > external software dependency and making your Makefile.am/configure.ac > more complex. Building libOpenCL.so instead of libpocl.so is easy > (you do it in 5 lines). The messy part will be to build and run > examples/test-suites in any available modes (direct link to libpocl, > link through ocl-icd libOpenCL.so and now link through libOpenCL.so > provided by pocl)
I do not have a strong opinion on this matter. IMO we can require ocl-icd at least for developers (and thus 'make check'), no problem there that I can see. Parboil seems to be an obscure case as it explicitly checks with ldd that the library linked against is called libOpenCL.so. But with ocl-icd it should work alright. This was just a quick fix to get the test suite linking without icd as I've been too busy/lazy to install ocl-icd yet. I'll see into it. -- Pekka ------------------------------------------------------------------------------ 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
