commit | 58c34f5a5b5c0eb165c4af169688a2271ebe55f0 | [log] [tgz] |
---|---|---|
author | David 'Digit' Turner <digit@google.com> | Mon Aug 12 14:11:58 2019 +0200 |
committer | David Turner <digit@google.com> | Wed Aug 14 07:00:18 2019 +0000 |
tree | 52f688bed90e73cd2b420fb7f7728620b66659e7 | |
parent | 3c80730148d7f91be89239cdaa47910cc07e2ee2 [diff] |
Support launching the VulkanUnitTests suite on Fuchsia. This small CL allows one to build and run the VulkanUnitTests suite for Fuchsia using the Chromium build system. Note that the output library generated by the BUILD.gn file is also renamed libvk_swiftshader.so to correspond to the name used by other build systems (e.g. CMakeList.txt and Android.{mk,bp}). This also avoids a Fuchsia-specific issue, where the packaging scripts under //build/fuchsia/ (in the Chromium src/ tree), get confused when a generated library has the same name as one of the system libraries (in this case, libvulkan.so, which is the Vulkan loader provided by the SDK, and which must be copied into the final Fuchsia package along the ICD). Note also that most tests crash inside the generated coroutine machine code :-/ Instructions to properly rebuild and test this: - Have depot_tools in your path, and a valid Chromium source checkout. - Ensure that your .gclient file contains 'fuchsia' in its `target_os` list variable definition, otherwise add it and run `gclient sync` again to fetch the Fuchsia SDK and other dependencies. - Create an output directory configured for a Fuchsia/x64 build, then rebuild the test suite target, e.g.: gn gen out/Fuchsia --args 'target_os="fuchsia" target_cpu="x64" \ use_goma = true \ root_extra_deps = [ \ "//third_party/swiftshader/tests/VulkanUnitTests:swiftshader_vulkan_unittests" \ ]' ninja -C out/Fuchsia swiftshader_vulkan_unittests - Run the test suite with the wrapper script: out/Fuchsia/bin/run_swiftshader_vulkan_unittests NOTE: This will start a QEMU instance running a Fuchsia system image automatically. + Define VK_USE_PLATFORM_FUCHSIA when building for Fuchsia. This will be used by future CLs that add support for Fuchsia-specific extensions. Change-Id: I687f51e98ee3cb16f6d585f44f4bb5f0631b1cd8 Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34911 Tested-by: David Turner <digit@google.com> Reviewed-by: Nicolas Capens <nicolascapens@google.com> Kokoro-Presubmit: kokoro <noreply+kokoro@google.com>
SwiftShader is a high-performance CPU-based implementation of the OpenGL ES and Direct3D 9 graphics APIs12. Its goal is to provide hardware independence for advanced 3D graphics.
SwiftShader libraries can be built for Windows, Linux, and Mac OS X.
Android and Chrome (OS) build environments are also supported.
Visual Studio
On Windows, open the SwiftShader.sln file using Visual Studio Community or compatible version, and build the solution. Output DLLs will be placed in the out subfolder. Sample executables such as OGLES3ColourGrading can be found under the Tests solution folder and can be run from the IDE.
CMake
Install CMake for Linux, Mac OS X, or Windows and use either the IDE or run the following terminal commands:
cd build cmake .. make --jobs=8 ./gles-unittests ./OGLES2HelloAPI
The SwiftShader libraries act as drop-in replacements for graphics drivers.
On Windows, most applications can be made to use SwiftShader's DLLs by placing them in the same folder as the executable. On Linux, the LD_LIBRARY_PATH environment variable or -rpath linker option can be used to direct applications to search for shared libraries in the indicated directory first.
See CONTRIBUTING.txt for important contributing requirements.
The canonical repository for SwiftShader is hosted at: https://swiftshader.googlesource.com/SwiftShader
All changes must be reviewed and approved in the Gerrit review tool at: https://swiftshader-review.googlesource.com
Authenticate your account here: https://swiftshader-review.googlesource.com/new-password
All changes require a Change-ID tag in the commit message. A commit hook may be used to add this tag automatically, and can be found at: https://gerrit-review.googlesource.com/tools/hooks/commit-msg. To clone the repository and install the commit hook in one go:
git clone https://swiftshader.googlesource.com/SwiftShader && (cd SwiftShader && curl -Lo `git rev-parse --git-dir`/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg ; chmod +x `git rev-parse --git-dir`/hooks/commit-msg)
Changes are uploaded to Gerrit by executing:
git push origin HEAD:refs/for/master
SwiftShader's OpenGL ES implementation can be tested using the dEQP test suite.
See docs/dEQP.md for details.
The third_party directory contains projects which originated outside of SwiftShader:
subzero contains a fork of the Subzero project. It is part of Google Chrome‘s (Portable) Native Client project. Its authoritative source is at https://chromium.googlesource.com/native_client/pnacl-subzero/. The fork was made using git-subtree to include all of Subzero’s history, and until further notice it should not diverge from the upstream project. Contributions must be tested using the README instructions, reviewed at https://chromium-review.googlesource.com, and then pulled into the SwiftShader repository.
llvm-subzero contains a minimized set of LLVM dependencies of the Subzero project.
PowerVR_SDK contains a subset of the PowerVR Graphics Native SDK for running several sample applications.
googletest contains the Google Test project, as a Git submodule. It is used for running unit tests for Chromium, and Reactor unit tests. Run git submodule update --init
to obtain/update the code. Any contributions should be made upstream.
See docs/Index.md.
Public mailing list: swiftshader@googlegroups.com
General bug tracker: https://g.co/swiftshaderbugs
Chrome specific bugs: https://bugs.chromium.org/p/swiftshader
The SwiftShader project is licensed under the Apache License Version 2.0. You can find a copy of it in LICENSE.txt.
Files in the third_party folder are subject to their respective license.
The legal authors for copyright purposes are listed in AUTHORS.txt.
CONTRIBUTORS.txt contains a list of names of individuals who have contributed to SwiftShader. If you‘re not on the list, but you’ve signed the Google CLA and have contributed more than a formatting change, feel free to request to be added.