diff options
Diffstat (limited to 'en/devices/graphics/build-tests.html')
| -rw-r--r-- | en/devices/graphics/build-tests.html | 43 |
1 files changed, 21 insertions, 22 deletions
diff --git a/en/devices/graphics/build-tests.html b/en/devices/graphics/build-tests.html index 3e280ab0..6b5049ea 100644 --- a/en/devices/graphics/build-tests.html +++ b/en/devices/graphics/build-tests.html @@ -35,15 +35,14 @@ compiling the test programs.</p> <p>CMake is an open source build system that supports multiple platforms and toolchains. CMake generates native makefiles or IDE project files from -target-independent configuration files. For more information on CMake, -please see the <a href="http://www.cmake.org/cmake/help/documentation.html">CMake</a> documentation.</p> +target-independent configuration files. For more information on CMake, please see the <a href="http://www.cmake.org/cmake/help/documentation.html">CMake</a> documentation.</p> <p>CMake supports and recommends out-of-source-tree builds, i.e., you should always create makefiles or project files in a separate build directory outside the source tree. CMake does not have any kind of "distclean" target, so removing any files generated by CMake must be done manually.</p> -<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> +<p>Configuration options are given to CMake using <code>-D<var>OPTION_NAME</var>=<var>VALUE</var></code> syntax. Some commonly used options for deqp are listed below.</p> <table> <tr> @@ -53,9 +52,9 @@ removing any files generated by CMake must be done manually.</p> <tr> <td><code>DEQP_TARGET</code></td> -<td><p>Target name, for example: "android"</p> +<td><p>Target name, for example: "android"</p> <p>The deqp CMake scripts will include the file -<code>targets/<DEQP_TARGET>/<DEQP_TARGET>.cmake</code> and expect to find target-specific build options from there.</p> +<code>targets/<var>DEQP_TARGET</var>/<var>DEQP_TARGET</var>.cmake</code> and expect to find target-specific build options from there.</p> </td> </tr> <tr> @@ -64,7 +63,7 @@ removing any files generated by CMake must be done manually.</p> </tr> <tr> <td><code>CMAKE_BUILD_TYPE</code></td> -<td><p>Build type for makefile targets. Valid values are: "Debug" and "Release"</p> +<td><p>Build type for makefile targets. Valid values are: "Debug" and "Release"</p> <p>Note the interpretation and default type depend on the targeted build system. See the CMake documentation for details.</p> </td> @@ -75,9 +74,9 @@ See the CMake documentation for details.</p> <p>The deqp build system is configured for new targets using target build files. A target build file defines which features the platform supports and what libraries or -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> +additional include paths are required. Target file names follow the <code>targets/<var>NAME</var>/<var>NAME</var>.cmake</code> format and the target is selected using the <code>DEQP_TARGET</code> build parameter.</p> -<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> +<p>File paths in target files are relative to the base <code>deqp</code> directory, not the <code>targets/<var>NAME</var></code> directory. The following standard variables can be set by target build file.</p> <table> <tr> @@ -173,14 +172,14 @@ compiler. The deqp has been tested with Visual Studio 2013.</p> <p>Visual Studio project files can be generated with the following command:</p> -<pre> +<pre class="devsite-terminal devsite-click-to-copy"> cmake path\to\src\deqp -G "Visual Studio 12" </pre> -<p>A 64-bit build can be made by selecting "Visual Studio <ver> Win64" as the build +<p>A 64-bit build can be made by selecting "Visual Studio <var>VERSION</var> Win64" as the build generator:</p> -<pre> +<pre class="devsite-terminal devsite-click-to-copy"> cmake path\to\src\deqp -G "Visual Studio 12 Win64" </pre> @@ -223,7 +222,7 @@ Build-tools <a href="http://developer.android.com/sdk/index.html#Other">packages <li><a href="https://www.python.org/downloads/">Python 2.6</a> or newer in 2.x series; Python 3.x is not supported <li>For Windows: Either NMake or JOM in <code>PATH</code> <ul> - <li><a href="http://qt-project.org/wiki/jom">JOM</a> enables faster builds + <li><a href="http://qt-project.org/wiki/jom">JOM</a> enables faster builds </ul> <li> Optional: Ninja make is also supported on Linux </ul> @@ -231,7 +230,7 @@ Build-tools <a href="http://developer.android.com/sdk/index.html#Other">packages <p>Ant and SDK binaries are located based on the PATH environment variable with certain overriding defaults. The logic is controlled by <code>android/scripts/common.py</code>. </p> -<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> +<p>The NDK directory must be either <code>~/android-ndk-<var>VERSION</var></code> or <code>C:/android/android-ndk-<var>VERSION</var></code> or defined via the <code>ANDROID_NDK_PATH</code> environment variable.</p> <p>Deqp on-device components, the test execution service, and test programs are 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> @@ -283,12 +282,12 @@ x11_egl_glx</code></td> <p>An example of a full command line used to do a 32-bit debug build against driver headers and libraries in a custom location is the following:</p> -<pre> -$ cmake <path to src>/deqp -DDEQP_TARGET=x11_egl -DCMAKE_C_FLAGS="-m32" +<pre class="devsite-click-to-copy"> +<code class="devsite-terminal">cmake <path to src>/deqp -DDEQP_TARGET=x11_egl -DCMAKE_C_FLAGS="-m32" -DCMAKE_CXX_FLAGS="-m32" -DCMAKE_BUILD_TYPE=Debug --DCMAKE_LIBRARY_PATH="<path to driver>/lib" --DCMAKE_INCLUDE_PATH="<path to driver>/inc" -$ make -j4 +-DCMAKE_LIBRARY_PATH="<var>PATH_TO_DRIVER</var>/lib" +-DCMAKE_INCLUDE_PATH="<var>PATH_TO_DRIVER</var>/inc"</code> +<code class="devsite-terminal">make -j4</code> </pre> <h2 id=cross-compiling>Cross-compiling</h2> @@ -334,10 +333,10 @@ DE_PTR_SIZE</code></td> <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> -<pre> -cmake <path to src>/deqp –DDEQP_BUILD_TYPE="Release" -–DCMAKE_TOOLCHAIN_FILE=<path to src>/delibs/cmake/toolchain-arm-cs.cmake -–DARM_CC_BASE=<path to cc directory> +<pre class="devsite-terminal devsite-click-to-copy"> +cmake <var>PATH_TO_SRC</var>/deqp –DDEQP_BUILD_TYPE="Release" +–DCMAKE_TOOLCHAIN_FILE=<var>PATH_TO_SRC</var>/delibs/cmake/toolchain-arm-cs.cmake +–DARM_CC_BASE=<var>PATH_TO_CC_DIRECTORY</var> </pre> <h2 id=run-time_linking_of_gles_and_egl_libraries>Run-time linking of GLES and EGL libraries</h2> |