C language headers for the OpenCL API; The Khronos Group (2013).
npm install opencl.csh
$ npm i opencl.c
`
And then include opencl.h as follows:
`c
// main.c
#include "node_modules/opencl.c/CL/opencl.h"
int main() { / ... / }
`
And then compile with clang or gcc as usual.
`bash
$ clang main.c # or, use gcc
$ gcc main.c
`
You may also use a simpler approach:
`c
// main.c
#include
int main() { / ... / }
`
If you add the path node_modules/opencl.c to your compiler's include paths.
`bash
$ clang -I./node_modules/opencl.c main.c # or, use gcc
$ gcc -I./node_modules/opencl.c main.c
`
Build instructions
> While the OpenCL Headers can be built and installed in isolation, it is part of the OpenCL SDK. If looking for streamlined build experience and a complete development package, refer to the SDK build instructions instead of the following guide.
$3
- The OpenCL Headers CMake package support uses CMake for its build system.
If CMake is not provided by your build system or OS package manager, please consult the CMake website.
$3
While the headers may just be copied as-is, this repository also contains a
CMake script with an install rule to allow for packaging the headers.
`bash
cmake -S . -B build -DCMAKE_INSTALL_PREFIX=/chosen/install/prefix
cmake --build build --target install
`
$3
Example CMake invocation
`bash
cmake -D CMAKE_PREFIX_PATH=/chosen/install/prefix /path/to/opencl/app
`
and sample CMakeLists.txt
`cmake
cmake_minimum_required(VERSION 3.0)
cmake_policy(VERSION 3.0...3.18.4)
project(proj)
add_executable(app main.cpp)
find_package(OpenCLHeaders REQUIRED)
target_link_libraries(app PRIVATE OpenCL::Headers)
`
Branch Structure
The OpenCL API headers in this repository are Unified headers and are designed
to work with all released OpenCL versions. This differs from previous OpenCL
API headers, where version-specific API headers either existed in separate
branches, or in separate folders in a branch.
Compiling for a Specific OpenCL Version
By default, the OpenCL API headers in this repository are for the latest
OpenCL version (currently OpenCL 3.0). To use these API headers to target
a different OpenCL version, an application may #define the preprocessor
value CL_TARGET_OPENCL_VERSION before including the OpenCL API headers.
The CL_TARGET_OPENCL_VERSION is a three digit decimal value representing
the OpenCL API version.
For example, to enforce usage of no more than the OpenCL 1.2 APIs, you may
include the OpenCL API headers as follows:
`c
#define CL_TARGET_OPENCL_VERSION 120
#include
`
Controlling Function Prototypes
By default, the OpenCL API headers in this repository declare function
prototypes for every known core OpenCL API and OpenCL extension API. If this is
not desired, the declared function prototypes can be controlled by the following
preprocessor defines:
* CL_NO_PROTOTYPES: No function prototypes will be declared. This control
applies to core OpenCL APIs and OpenCL extension APIs.
* CL_NO_CORE_PROTOTYPES: No function prototypes will be declared for core
OpenCL APIs.
* CL_NO_EXTENSION_PROTOTYPES: No function prototypes will be declared for
OpenCL extension APIs. This control applies to all OpenCL extension APIs.
* CL_NO_ICD_DISPATCH_EXTENSION_PROTOTYPES: No function prototypes will be
declared for OpenCL extension APIs that are in the ICD dispatch table for
historical reasons.
* CL_NO_NON_ICD_DISPATCH_EXTENSION_PROTOTYPES: No function prototypes will be
declared for OpenCL extension APIs that are not in the ICD dispatch table.
For example, to declare function prototypes for core OpenCL 3.0 APIs only, you
may include the OpenCL API headers as follows:
`c
#define CL_TARGET_OPENCL_VERSION 300
#define CL_NO_EXTENSION_PROTOTYPES
#include
`
Compatibility Notes
OpenCL values backward compatibility and in most cases an application using an
older version of the OpenCL API headers can seamlessly update to a newer version
of the OpenCL API headers. In rare cases, though, the OpenCL API headers may
break backward compatibility:
* Very rarely, there may be bugs or other issues in the OpenCL API headers that
cannot be fixed without breaking compatibility.
* The OpenCL API headers for beta features or beta extensions may
be changed in a way that breaks compatibility.
Applications or libraries that require stable OpenCL API headers are encouraged
to use tagged or released OpenCL API headers. We will do our best to document
any breaking changes in the description of each release. The OpenCL API headers
are tagged at least as often as each OpenCL specification release.
Beta Extensions
Beta extensions are extensions that are still in development and are
hence subject to change. To further improve compatibility for applications that
do not use beta features, support for beta extensions must be
explicitly enabled. Support for beta extensions is controlled by the
CL_ENABLE_BETA_EXTENSIONS preprocessor define.
For example, to enable support for OpenCL 3.0 APIs and all extensions, including
beta extensions, you may include the OpenCL API headers as follows:
`c
#define CL_TARGET_OPENCL_VERSION 300
#define CL_ENABLE_BETA_EXTENSIONS
#include
`
Directory Structure
`
README.md This file
LICENSE Source license for the OpenCL API headers
CL/ Unified OpenCL API headers tree
scripts/ Scripts for generating OpenCL extension headers
tests/ OpenCL API header tests
``