From bf6544c0ab0625e5ce5918f6d861763d4fa87aba Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Mon, 8 Dec 2014 09:29:28 +0200 Subject: Don't treat clew as part of an "external" clcc module There is no obvious authoritative upstream for clew anyway, so it causes philosophical problems for distros. For a while, we used to use a zip archive from the "clcc" project on SourceForge that included clew.c and clew.h. (Before that we also just had clew.c and clew.h in our source repo.) So, drop the external/clcc module and have clew.c and clew.h in the source repo again. But this time clew is in a module of its own, not in sc. This re-introduces "No need to have OpenCL optional at configure-time" This reverts commit 764836cb00e8e6dfd2ab48e080a166ec90359e01. Change-Id: I413142f4f9f8399489f9c3e5327132822f07a454 Reviewed-on: https://gerrit.libreoffice.org/13368 Reviewed-by: David Tardon Tested-by: David Tardon --- sc/workben/opencl/platform_detect.cxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sc/workben') diff --git a/sc/workben/opencl/platform_detect.cxx b/sc/workben/opencl/platform_detect.cxx index ef4558818d24..5fb2544c54cc 100644 --- a/sc/workben/opencl/platform_detect.cxx +++ b/sc/workben/opencl/platform_detect.cxx @@ -3,7 +3,7 @@ #include #include -#include "clew.h" +#include using namespace std; -- cgit