computecpp-sdk | using ComputeCpp , Codeplay 's SYCL implementation | GPU library

On the Codeplay website there is a step-by-step guide to building and running the ComputeCpp SDK samples. There is also a guide to SYCL that serves as an introduction to SYCL development. Additionally, there is an Integration guide should you wish to add ComputeCpp to existing projects.
CMake files are provided as a build system for this software. CMake version 3.4.3 is required at minimum, though later versions of CMake should continue to be compatible. At minimum, one CMake variable is required to get the sample code building - ComputeCpp_DIR. This variable should point to the root directory of the ComputeCpp install (i.e. the directory with the the folders bin, include, lib and so on). You can also specify COMPUTECPP_SDK_BUILD_TESTS to add the tests/ subdirectory to the build, which will build Gtest-based programs testing the legacy pointer and virtual pointer classes. Some samples have optional OpenMP support. You can enable it by setting COMPUTECPP_SDK_USE_OPENMP to ON in CMake. You can additionally specify CMAKE_BUILD_TYPE and CMAKE_INSTALL_PREFIX to choose a Debug or Release build and the location you’d like to be used when the "install" target is built. The install target currently will copy all the sample binaries to the directory of your choosing. Lastly, the SDK will build targeting spir64 IR by default. This will work on most devices, but won’t work on NVIDIA (for example). To that end, you can specify -DCOMPUTECPP_BITCODE=target, which can be any of spir[64], spirv[64] or ptx64. It is possible to specify multiple targets to COMPUTECPP_BITCODE, as a CMake list. Note that only the Professional Edition of ComputeCpp supports building multiple device targets. If you would like to crosscompile the SDK targeting some other platform, there are toolchain files available in the cmake/toolchains directory. They require certain variables pointing to the root of the toolchain you are using to be set in the environment. They cannot be specificed in the CMake cache. The toolchains will identify which variables have not been set when used.