commit | b25e892b7c6d4f1c47379286e0272140e3e09cd3 | [log] [tgz] |
---|---|---|
author | Doug Horn <doughorn@google.com> | Thu Jan 07 14:41:36 2021 -0800 |
committer | Doug Horn <doughorn@google.com> | Thu Jan 07 14:41:36 2021 -0800 |
tree | ab2e9036425214370c1bd2342f0be5aeb939bf79 | |
parent | d064a1d224383f4f186608e9539b5ceae594a842 [diff] |
darwin-aarch64: add MoltenVK and enable Vulkan by default Change-Id: I229885fcd75327f630f7398a14080de7d54b423d
Graphics Streaming Kit is a code generator that makes it easier to serialize and forward graphics API calls from one place to another:
Make sure the latest CMake is installed. Make sure you are using Clang as your CC
and CXX
. Then
mkdir build cd build cmake . ../ make -j24
Make sure the latest CMake is installed. Make sure Visual Studio 2019 is installed on your system along with all the Clang C++ toolchain components. Then
mkdir build cd build cmake . ../ -A x64 -T ClangCL
A solution file should be generated. Then open the solution file in Visual studio and build the gfxstream_backend
target.
Be in the Android build system. Then
m libgfxstream_backend
It then ends up in out/host
libgfxstream_backend.(dll|so|dylib)
There are a bunch of test executables generated. They require libEGL.so
and libGLESv2.so
and libvulkan.so
to be available, possibly from your GPU vendor or ANGLE, in the $LD_LIBRARY_PATH
.
There are a bunch of test executables generated. They require libEGL.dll
and libGLESv2.dll
and vulkan-1.dll
to be available, possibly from your GPU vendor or ANGLE, in the %PATH%
.
These are currently not built due to the dependency on system libEGL/libvulkan to run correctly.
CMakeLists.txt
: specifies all host-side build targets. This includes all backends along with client/server setups that live only on the host. SomeAndroid.bp
: specifies all guest-side build targets for Android:BUILD.gn
: specifies all guest-side build targets for Fuchsiabase/
: common libraries that are built for both the guest and host. Contains utility code related to synchronization, threading, and suballocation.protocols/
: implementations of protocols for various graphics APIs. May contain code generators to make it easy to regen the protocol based on certain things.host-common/
: implementations of host-side support code that makes it easier to run the server in a variety of virtual device environments. Contains concrete implementations of auxiliary virtual devices such as Address Space Device and Goldfish Pipe.stream-servers/
: implementations of various backends for various graphics APIs that consume protocol. gfxstream-virtio-gpu-renderer.cpp
contains a virtio-gpu backend implementation.