03.09.2012 10:53, ext Vincent Danjean skrev: >> -a libOpenCL->libpocl link can be made if exporting is enabled, adding >> this check to the currently available ones. Perhaps even with a user >> override to dissallow? > > I would propose that this link requires an explicit separate configure > option. By default, as proposed, we will build ICD and export symbols. > But, by default, we wont want that 'make install' overwrite libOpenCL.so > installed in the system (ICD loader).
I think the current checks check for the exsitance of libOpenCL before making the link. Why did we want this link there in the first place? > Note that the "-Wl,-z,defs" linker option I use will warn the developer > immediately if he uses a undefined symbol (ie clXXX instead of POclXXX). > It is the way I found all the clXXX to replace. Ok, lets add those, if not already in the proposed merge branch. kalle -- But beware the debugger. Dark side of the source it is. If once you start down the dark path, forever will it dominate your destiny. Consume you it will. ------------------------------------------------------------------------------ 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
