opencl: Use a different profiling macro

Enabling profiling in OpenCL effects the performance, so for
profiling libfreenect2s processors, it should be disabled and only
used when testing improvements of the OpenCL code itself.

Author: Thiemo Wiedemeyer

src/opencl_depth_packet_processor.cpp

@@ -225,7 +225,7 @@ class OpenCLDepthPacketProcessorImpl: public WithPerfLogging
   bool programInitialized;
   std::string sourceCode;
 
-#if LIBFREENECT2_WITH_PROFILING
+#ifdef LIBFREENECT2_WITH_PROFILING_CL
   std::vector<double> timings;
   int count;
 #endif
@@ -454,7 +454,7 @@ class OpenCLDepthPacketProcessorImpl: public WithPerfLogging
 
   bool initBuffers()
   {
-#if LIBFREENECT2_WITH_PROFILING
+#ifdef LIBFREENECT2_WITH_PROFILING_CL
     count = 0;
     CHECK_CL_PARAM(queue = cl::CommandQueue(context, device, CL_QUEUE_PROFILING_ENABLE, &err));
 #else
@@ -580,7 +580,7 @@ class OpenCLDepthPacketProcessorImpl: public WithPerfLogging
     CHECK_CL_RETURN(eventReadIr.wait());
     CHECK_CL_RETURN(eventReadDepth.wait());
 
-#if LIBFREENECT2_WITH_PROFILING
+#ifdef LIBFREENECT2_WITH_PROFILING_CL
     if(count == 0)
     {
       timings.clear();