G-API Standard backends

G-API backends available in this OpenCV version. More...

Functions
cv::gapi::GBackend	cv::gapi::fluid::backend ()
	Get a reference to Fluid backend. More...
cv::gapi::GBackend	cv::gapi::ocl::backend ()
	Get a reference to OCL backend. More...
cv::gapi::GBackend	cv::gapi::cpu::backend ()
	Get a reference to CPU (OpenCV) backend. More...

Detailed Description

G-API backends available in this OpenCV version.

G-API backends play a corner stone role in G-API execution stack. Every backend is hardware-oriented and thus can run its kernels efficiently on the target platform.

Backends are usually "back boxes" for G-API users – on the API side, all backends are represented as different objects of the same class cv::gapi::GBackend. User can manipulate with backends mainly by specifying which kernels to use or where to look up for kernels first.

See also

High-level design overview, cv::gapi::lookup_order()

Function Documentation

backend() [1/3]

cv::gapi::GBackend cv::gapi::fluid::backend

(

)

Get a reference to Fluid backend.

See also

G-API Standard backends

backend() [2/3]

cv::gapi::GBackend cv::gapi::ocl::backend

(

)

Get a reference to OCL backend.

At the moment, the OCL backend is built atop of OpenCV "Transparent API" (T-API), see cv::UMat for details.

See also

G-API Standard backends

backend() [3/3]

cv::gapi::GBackend cv::gapi::cpu::backend

(

)

Get a reference to CPU (OpenCV) backend.

This is the default backend in G-API at the moment, providing broader functional coverage but losing some graph model advantages. Provided mostly for reference and prototyping purposes.

See also

G-API Standard backends