Lines Matching full:code
48 <p>Configuration options are given to CMake using <code>-D<OPTION_NAME>=<VALUE></code> syntax. Some commonly used options for deqp are listed below.</p>
57 <td><code>DEQP_TARGET</code></td>
60 <code>targets/<DEQP_TARGET>/<DEQP_TARGET>.cmake</code> and expect to find target-specific build options from there.</p>
64 <td><code>CMAKE_TOOLCHAIN_FILE</code></td>
68 <td><code>CMAKE_BUILD_TYPE</code></td>
80 additional include paths are required. Target file names follow the <code>targets/<name>/<name>.cmake</code> format and the target is selected using the <code>DEQP_TARGET</code> build parameter.</p>
82 <p>File paths in target files are relative to the base <code>deqp</code> directory, not the <code>targets/<name></code> directory. The following standard variables can be set by target build file.</p>
90 <td><code>
91 DEQP_TARGET_NAME</code></td>
96 <td><code>
97 DEQP_SUPPORT_GLES2</code></td>
102 <td><code>
103 DEQP_GLES2_LIBRARIES</code></td>
108 <td><code>
109 DEQP_SUPPORT_GLES3</code></td>
114 <td><code>
115 DEQP_GLES3_LIBRARIES</code></td>
120 <td><code>
121 DEQP_SUPPORT_VG</code></td>
126 <td><code>
127 DEQP_OPENVG_LIBRARIES</code></td>
132 <td><code>
133 DEQP_SUPPORT_EGL</code></td>
138 <td><code>
139 DEQP_EGL_LIBRARIES</code></td>
144 <td><code>
145 DEQP_PLATFORM_LIBRARIES</code></td>
150 <td><code>
151 DEQP_PLATFORM_COPY_LIBRARIES</code></td>
158 <td><code>
159 TCUTIL_PLATFORM_SRCS</code></td>
163 <p><strong>Note:</strong> Paths are relative to: <code>framework/platform</code></p>
168 <p>The target build file can add additional include or link paths using the <code>include_directories()</code> and <code>link_directories()</code> CMake functions.</p>
189 <p>You can also generate NMake makefiles with the <code>-G "NMake Makefiles"</code> option as well as the build type (<code>-DCMAKE_BUILD_TYPE="Debug"</code> or <code>"Release"</code>).</p>
198 standard libraries. WGL context can be selected using the <code>--deqp-gl-context-type=wgl</code> command line argument. In the WGL mode, the deqp uses the <code>WGL_EXT_create_context_es_profile</code> extension to create OpenGL ES contexts. This has been tested to work with
207 parameter: <code>--deqp-gl-context-type=egl</code></p>
211 <p>The Android build uses CMake build scripts for building the native test code.
219 <li>The latest version of the <a href="http://developer.android.com/tools/sdk/ndk/index.html">Android NDK</a>; the <code>android/scripts/common.py</code> file lists the required version
223 (required by the Java code build)
226 <li>For Windows: Either NMake or JOM in <code>PATH</code>
234 certain overriding defaults. The logic is controlled by <code>android/scripts/common.py</code>. </p>
236 <p>The NDK directory must be either <code>~/android-ndk-<version></code> or <code>C:/android/android-ndk-<version></code> or defined via the <code>ANDROID_NDK_PATH</code> environment variable.</p>
239 built by executing the <code>android/scripts/build.py</code> script. The final .apk is created in <code>android/package/bin</code> and can be installed by the <code>install.py</code> script. If the <a href="port-tests.html#test_execution_service">command line executor</a> is used, the ExecService is launched with <code>launch.py</code> script on the device via ADB. The scripts can be executed from any directory.</p>
252 <td><code>default</code></td>
258 <td><code>
259 x11_glx</code></td>
265 <td><code>
266 x11_egl</code></td>
272 <td><code>
273 x11_egl_glx</code></td>
279 <p>Always use <code>-DCMAKE_BUILD_TYPE=<Debug|Release></code> to define the build type. <code>Release</code> is a good default. Without it, a default, unoptimized release build is made.</p>
281 <p>The <code>-DCMAKE_C_FLAGS</code> and <code>-DCMAKE_CXX_FLAGS</code> command line arguments can be used to pass extra arguments to the compiler. For example the 32-bit or 64-bit build can be done by setting <code>-DCMAKE_C(XX)_FLAGS="-m32"</code> or <code>"-m64"</code> respectively. If not specified, the toolchain native architecture, typically 64-bit on the 64-bit toolchain, is used.</p>
283 <p>The <code>-DCMAKE_LIBRARY_PATH</code> and <code>-DCMAKE_INCLUDE_PATH</code> arguments can be used for CMake to give CMake additional library or include search paths.</p>
301 included in the release package in the <code>framework/delibs/cmake</code> directory.</p>
304 can be set by the toolchain file. CMake can usually detect <code>DE_OS</code>, <code>DE_COMPILER</code> and <code>DE_PTR_SIZE</code> correctly but <code>DE_CPU</code> must be set by the toolchain file.</p>
312 <td><code>
313 DE_OS</code></td>
314 <td><p>Operating system. Supported values are: <code>DE_OS_WIN32, DE_OS_UNIX, DE_OS_WINCE, DE_OS_OSX, DE_OS_ANDROID, DE_OS_SYMBIAN, DE_OS_IOS</code></p>
318 <td><code>
319 DE_COMPILER</code></td>
320 <td><p>Compiler type. Supported values are: <code>DE_COMPILER_GCC, DE_COMPILER_MSC, DE_COMPILER_CLANG</code></p>
324 <td><code>
325 DE_CPU</code></td>
326 <td><p>CPU type. Supported values are: <code>DE_CPU_ARM, DE_CPU_X86</code>.</p>
330 <td><code>
331 DE_PTR_SIZE</code></td>
337 <p>The toolchain file can be selected using the <code>CMAKE_TOOLCHAIN_FILE</code> build parameter. For example, the following would create makefiles for a build using the CodeSourcery cross-compiler for ARM/Linux:</p>
348 test code always accesses the APIs through function pointers. Entry points can
354 static linking is desired, provide the needed link libraries in the <code>DEQP_<API>_LIBRARIES</code> build configuration variable.</p>
