encounter
/
dawn-cmake
mirror of https://github.com/encounter/dawn-cmake.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
dawn-cmake/BUILD.gn

1238 lines
41 KiB
Plaintext
Raw Normal View History

Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
# Copyright 2018 The Dawn Authors
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
Build with a different gtest harness when in Chromium Running test in a Chromium build requires using their gtest and gmock targets as well as a harness that is in //base. Since we want to run Dawn tests on the Chromium GPU bots, we need to support two configurations both building tests standalone and in Chromium. BUG=chromium:870747 Change-Id: I862e62a607e193a27562ece0f1f6d46d8728e446 Reviewed-on: https://dawn-review.googlesource.com/c/2080 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Stephen White <senorblanco@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2018-10-31 10:49:21 +00:00
import("//build_overrides/build.gni")
Add Vulkan validation layers on Windows Deploy self-built Vulkan validation layers instead of system installed one. And it will reuse third_party/angle's Vulkan validation layers if building with chromium. Bug: dawn:150 Change-Id: I94e26f7a152fb2a1c39bcb102d60024f4d65eee6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11120 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-11-07 12:13:27 +00:00
import("//build_overrides/vulkan_validation_layers.gni")
dawn_native: handle NaN lod values in samplers For samplers with NaN mLodMinClamp or mLodMaxClamp, the equality operator returned false. Adds checks for finite values, and also early returns if two pointers are equal. Bug: dawn:143, chromium:965633 Change-Id: Id5998d6eec275af0fbe30e3b4fcb3eed4fe64c6a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7401 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Idan Raiter <idanr@google.com>
2019-05-22 17:18:52 +00:00
import("generator/dawn_generator.gni")
BUILD.gn: Split dawn_component/generator in their own files This will allow follow up commits to use them from the different parts of the split-off BUILD.gn file. BUG=dawn:61 Change-Id: I767f6c97c06ee73290d3df482880d1a2df92e187 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5301 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-06 23:17:39 +00:00
import("scripts/dawn_component.gni")
[dawn] small fix for BUILD.gn BackendBinding.h includes dawn/dawncpp.h, so dawn_headers_gen needs to be in public_deps. See below reference for more details. https://gn.googlesource.com/gn/+/master/docs/reference.md#var_public_deps Applied `gn format` too. Bug: chromium:931596 Change-Id: I8572ba54b56c96950a58ec068ba797b3031f3c01 Reviewed-on: https://dawn-review.googlesource.com/c/4640 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-02-13 18:42:38 +00:00
import("scripts/dawn_features.gni")
import("scripts/dawn_overrides_with_defaults.gni")
Revert "Create new src/tests BUILD.gn file." This reverts commit 672d29d14c26e39341d75b8d1dc1a4e7ee4b6f66. Reason for revert: https://bugs.chromium.org/p/chromium/issues/detail?id=913171 Original change's description: > Create new src/tests BUILD.gn file. > > Move all test-related build stuff into its own BUILD.gn file. This > required moving the dawn_generator template into a common file, so it > can be called by both BUILD.gn and src/tests/BUILD.gn. > > [This is a reland of https://dawn-review.googlesource.com/c/dawn/+/2940 > with a fix for mock_dawn.] > > Bug: dawn:61 > Change-Id: Id1e6d0c2b07caa2610cebe206511e972ac18fe8d > Reviewed-on: https://dawn-review.googlesource.com/c/3020 > Reviewed-by: Kai Ninomiya <kainino@chromium.org> > Reviewed-by: Corentin Wallez <cwallez@chromium.org> > Commit-Queue: Stephen White <senorblanco@chromium.org> TBR=cwallez@chromium.org,kainino@chromium.org,senorblanco@chromium.org Change-Id: I54cdc558b128935dc8a8d22ec2b5e879271c35ae No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: dawn:61 Reviewed-on: https://dawn-review.googlesource.com/c/3080 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2018-12-08 10:35:53 +00:00
import("//testing/test.gni")
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
Allow using swiftshader with the Vulkan backend This adds swiftshader as a dependency of Dawn, and when it is present dawn_use_swiftshader=true will force usage of it. (due to a Vulkan loader limitation we can't have both regular drivers and swiftshader in the same VkInstance). BUG=dawn:283 Change-Id: Ib94f4dcca652eb380e994f007cdcfb145b1a5102 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13440 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-11-26 18:21:51 +00:00
# Swiftshader is an optional dependency of Dawn so we only use it if the path
# to it has been set.
use_swiftshader = dawn_use_swiftshader && dawn_swiftshader_dir != ""
if (use_swiftshader) {
assert(dawn_enable_vulkan,
"dawn_use_swiftshader requires dawn_enable_vulkan=true")
import("${dawn_swiftshader_dir}/src/Vulkan/vulkan.gni")
}
Re-enable -Wunguarded-availability in Dawn standalone builds By bumping the min macOS SDK version for standalone Dawn builds we are able to re-introduce -Wunguarded-availability, which will help prevent usage of Metal APIs without correctly checking for their availability. BUG= Change-Id: Iebf2f64e9f68e2a7a90fc6f3f208967f952f3487 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11400 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-12-11 16:54:51 +00:00
# Import mac_min_system_version
if (is_mac) {
import("//build/config/mac/mac_sdk.gni")
}
Add dawn_platform::Platform for handling tracing events in Dawn This patch provides Chromium TRACE_EVENT macros and hooks for implementing the TRACE_EVENT api. Bug: chromium:958013 Change-Id: I033b1c7ca57c550504a1bea1898a1a152831922b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7060 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-13 19:00:34 +00:00
###############################################################################
# dawn_platform
###############################################################################
source_set("dawn_platform") {
configs += [ "${dawn_root}/src/common:dawn_internal" ]
sources = [
"${dawn_root}/src/include/dawn_platform/DawnPlatform.h",
"src/dawn_platform/tracing/EventTracer.cpp",
"src/dawn_platform/tracing/EventTracer.h",
"src/dawn_platform/tracing/TraceEvent.h",
]
deps = [
"${dawn_root}/src/common",
]
}
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
###############################################################################
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
# libdawn_native
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
###############################################################################
config("libdawn_native_internal") {
Split off common and libdawn / dawn_headers from BUILD.gn This adds an option to dawn_generator to generate files in a different directory so the generated stay at the same place. Otherwise compilation errors occur because of stale versions of the headers on the CQ builders. BUG=dawn:61 Change-Id: I71ceb3172b5a4e35911973a03be29d90fa684416 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5304 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-07 01:46:39 +00:00
configs = [ "${dawn_root}/src/common:dawn_internal" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
Clarify disabled warning for Metal in BUILD.gn BUG= Change-Id: I7f0715bbaaae433d2f1a93c5a2496f28d466e150 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11220 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:40:32 +00:00
# Suppress warnings that Metal isn't in the deployment target of Chrome:
# initialization of the Metal backend is behind a IsMetalSupported check so
# Dawn won't call Metal functions on macOS 10.10.
Re-enable -Wunguarded-availability in Dawn standalone builds By bumping the min macOS SDK version for standalone Dawn builds we are able to re-introduce -Wunguarded-availability, which will help prevent usage of Metal APIs without correctly checking for their availability. BUG= Change-Id: Iebf2f64e9f68e2a7a90fc6f3f208967f952f3487 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11400 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-12-11 16:54:51 +00:00
# At the time this is written Chromium supports 10.10.0 and above, so if we
# aren't on 10.11 it means we are on 10.11 and above, and Metal is available.
# Skipping this check on 10.11 and above is important as it allows getting
# proper compilation warning when using 10.12 and above feature for example.
Clarify disabled warning for Metal in BUILD.gn BUG= Change-Id: I7f0715bbaaae433d2f1a93c5a2496f28d466e150 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11220 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:40:32 +00:00
# TODO(cwallez@chromium.org): Consider using API_AVAILABLE annotations on all
Re-enable -Wunguarded-availability in Dawn standalone builds By bumping the min macOS SDK version for standalone Dawn builds we are able to re-introduce -Wunguarded-availability, which will help prevent usage of Metal APIs without correctly checking for their availability. BUG= Change-Id: Iebf2f64e9f68e2a7a90fc6f3f208967f952f3487 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11400 Reviewed-by: Nico Weber <thakis@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-12-11 16:54:51 +00:00
# metal code in dawn once crbug.com/1004024 is sorted out if Chromium still
# supports 10.10 then.
if (is_mac && mac_min_system_version == "10.10.0") {
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
cflags_objcc = [ "-Wno-unguarded-availability" ]
}
}
Metal.framework must be optional instead of hard requirement. It's required to execute binary on Mac 10.10. Problem has been revealed after integrating 1002023. It's not visible by default, because clang under the hood changes hard requirement to optional. See: - https://chromium-review.googlesource.com/c/chromium/src/+/1792702 - https://bugs.chromium.org/p/chromium/issues/detail?id=1003381 discussion. Bug: chromium:1003381 Change-Id: I46e8da1092748256985ca4c2b90244f2ac5d422c Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12540 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-10-21 11:35:49 +00:00
config("libdawn_native_weak_framework") {
if (is_mac && dawn_enable_metal) {
ldflags = [
"-weak_framework",
"Metal",
]
}
}
Generators: main.py is now dawn_json_generator.py This merges all the files for main.py together again except generator_lib.py because there doesn't seeem to be a good way to separate the pure dawn.json generators and the dawn wire generator. Also updates the GN templates to make it easier to define new generators based on generator_lib, and move the Jinja2 template "stdlib" to generator_lib.py BUG=dawn:165 Change-Id: I1b5b2ef0a59cb142e214f3af9a58048a88ae949a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7880 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-06-11 18:03:05 +00:00
dawn_json_generator("libdawn_native_utils_gen") {
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
target = "dawn_native_utils"
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
outputs = [
Normalize generated file paths to match main tree. Previously dawn_native files were in src/dawn_native/ while generated files were in dawn_native/. This makes some things complicated when integrating in other source trees so normalize all generated files to be in paths that match the main tree. BUG=dawn:225 Change-Id: I5b3e04d37a16251143578dfb7a31445b229fe4ac Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11300 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:33:12 +00:00
"src/dawn_native/ProcTable.cpp",
Make dawn_native use the webgpu.h header BUG=dawn:22 Change-Id: I66e2d998f5e09030e40ec88813cd65c492018fd0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12541 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-10-23 11:57:41 +00:00
"src/dawn_native/wgpu_structs_autogen.h",
"src/dawn_native/wgpu_structs_autogen.cpp",
Normalize generated file paths to match main tree. Previously dawn_native files were in src/dawn_native/ while generated files were in dawn_native/. This makes some things complicated when integrating in other source trees so normalize all generated files to be in paths that match the main tree. BUG=dawn:225 Change-Id: I5b3e04d37a16251143578dfb7a31445b229fe4ac Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11300 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:33:12 +00:00
"src/dawn_native/ValidationUtils_autogen.h",
"src/dawn_native/ValidationUtils_autogen.cpp",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
}
OpenGL: Don't use glad to load OpenGL entrypoints This makes the OpenGL entry points loaded at Adapter creation from the getProcAddress passed in the DiscoveryOptions and update all GL calls in the backend to go through the new OpenGLFunctions object. A code generator is added that generates the function loader and list of GL procs from Khronos' gl.xml file but we can't get rid of glad yet because it is used to have the PROC typedefs and enum values. BUG=dawn:165 Change-Id: I2a583d79752f55877fa4190846f5be16cf91651a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7983 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-13 10:22:32 +00:00
if (dawn_enable_opengl) {
dawn_generator("libdawn_native_opengl_loader_gen") {
script = "generator/opengl_loader_generator.py"
args = [
"--gl-xml",
Remove glad and replace it with our own GL header This completely removes the dependency on glad by generating the GL headers from gl.xml directly. This requires adding khrplatform.h so all Khronos dependencies are gathered in third_party/khronos. Also removes a stray CMakeLists.txt that was still hanging out. BUG=dawn:165 Change-Id: Ia64bc51bc8b18c6b48613918e2f309f7405ecb3b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8163 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-17 09:17:29 +00:00
rebase_path("third_party/khronos/gl.xml", root_build_dir),
OpenGL: Support B2T and T2T copies with BC formats This patch implements the creation, buffer-to-texture copies and texture-to-texture copies with BC formats on OpenGL backend. Note that OpenGL SPEC also has the same issue about texture-to-texture copies with compressed textures as Vulkan SPEC, so we have to skip the related case. The texture-to-buffer copies with BC formats and related end2end tests will be supported in the following patches. BUG=dawn:42 TEST=dawn_end2end_tests Change-Id: I76b16862259cb2df77f202ed7ed433d41aa3cd47 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/10220 Commit-Queue: Jiawei Shao <jiawei.shao@intel.com> Reviewed-by: Austin Eng <enga@chromium.org>
2019-08-22 08:19:13 +00:00
"--supported-extensions",
rebase_path("src/dawn_native/opengl/supported_extensions.json",
root_build_dir),
OpenGL: Don't use glad to load OpenGL entrypoints This makes the OpenGL entry points loaded at Adapter creation from the getProcAddress passed in the DiscoveryOptions and update all GL calls in the backend to go through the new OpenGLFunctions object. A code generator is added that generates the function loader and list of GL procs from Khronos' gl.xml file but we can't get rid of glad yet because it is used to have the PROC typedefs and enum values. BUG=dawn:165 Change-Id: I2a583d79752f55877fa4190846f5be16cf91651a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7983 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-13 10:22:32 +00:00
]
outputs = [
Normalize generated file paths to match main tree. Previously dawn_native files were in src/dawn_native/ while generated files were in dawn_native/. This makes some things complicated when integrating in other source trees so normalize all generated files to be in paths that match the main tree. BUG=dawn:225 Change-Id: I5b3e04d37a16251143578dfb7a31445b229fe4ac Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11300 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:33:12 +00:00
"src/dawn_native/opengl/OpenGLFunctionsBase_autogen.cpp",
"src/dawn_native/opengl/OpenGLFunctionsBase_autogen.h",
"src/dawn_native/opengl/opengl_platform_autogen.h",
OpenGL: Don't use glad to load OpenGL entrypoints This makes the OpenGL entry points loaded at Adapter creation from the getProcAddress passed in the DiscoveryOptions and update all GL calls in the backend to go through the new OpenGLFunctions object. A code generator is added that generates the function loader and list of GL procs from Khronos' gl.xml file but we can't get rid of glad yet because it is used to have the PROC typedefs and enum values. BUG=dawn:165 Change-Id: I2a583d79752f55877fa4190846f5be16cf91651a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7983 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-13 10:22:32 +00:00
]
}
}
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
# Public libdawn_native headers so they can be publically visible for
# dependencies of libdawn_native
source_set("libdawn_native_headers") {
public_deps = [
Split generation of dawncpp headers from libdawncpp libdawn_native also requires the dawncpp headers. When we separated libdawn_cpp from the dawn_headers, libdawn_native lost the cpp headers and caused a compile failure. This patch separates the dawncpp headers as a separate target so both libdawncpp and libdawn_native can depend on them. Bug: dawn:22 Change-Id: I4172f1654377afac8c4314123ee8b5b81dc7c928 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12300 Reviewed-by: David Turner <digit@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-10-16 10:26:01 +00:00
"${dawn_root}/src/dawn:dawncpp_headers",
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
]
BUILD.gn: put public include dirs in all_dependent_configs The public include dirs for Dawn were in the dawn_public config but it would only be added to targets as a part of public_configs. This meant that second-level dependencies that ended up needing to include dawn/dawn.h wouldn't know where to find it. Fixed this by adding include dirs in all_dependent_configs and renamed the config to be very explicit that it is for include dirs only. BUG=chromium:938895 Change-Id: Iad70f3ce1f8a02b96bf341e7dd7d6068ce645af7 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5920 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-26 17:16:28 +00:00
all_dependent_configs = [ "${dawn_root}/src/common:dawn_public_include_dirs" ]
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
sources = [
"src/include/dawn_native/DawnNative.h",
"src/include/dawn_native/dawn_native_export.h",
# Include all backend's public headers so that dependencies can include
# them even when the backends are disabled.
"src/include/dawn_native/D3D12Backend.h",
"src/include/dawn_native/MetalBackend.h",
"src/include/dawn_native/NullBackend.h",
"src/include/dawn_native/OpenGLBackend.h",
"src/include/dawn_native/VulkanBackend.h",
]
}
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
# The meat of the compilation for libdawn_native so that we can cheaply have
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
# shared_library / static_library versions of it. It compiles all the files
# except those that define exported symbols.
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
source_set("libdawn_native_sources") {
deps = [
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
":libdawn_native_headers",
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
":libdawn_native_utils_gen",
Split off common and libdawn / dawn_headers from BUILD.gn This adds an option to dawn_generator to generate files in a different directory so the generated stay at the same place. Otherwise compilation errors occur because of stale versions of the headers on the CQ builders. BUG=dawn:61 Change-Id: I71ceb3172b5a4e35911973a03be29d90fa684416 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5304 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-07 01:46:39 +00:00
"${dawn_root}/src/common",
Use spvc's rules for spirv-cross Switch over to using the rule for building spirv-cross from spvc. This allows GN to avoid double symbol issues in future patches. Roll third_party/shaderc/ 1d6155d86..30f0559dd (2 commits) https://chromium.googlesource.com/external/github.com/google/shaderc/+log/1d6155d8679a..30f0559dd278 $ git log 1d6155d86..30f0559dd --date=short --no-merges --format='%ad %ae %s' 2019-11-27 rharrison Remove spvc's dependency on shaderc's util library (#914) 2019-11-27 rharrison Clean up how include dirs are propegated for spirv_cross (#912) Created with: roll-dep third_party/shaderc BUG=dawn:281 Change-Id: I49cf237dcab884e84180f83cbbb21acfa549fe61 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/14121 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Ryan Harrison <rharrison@chromium.org>
2019-11-28 17:14:55 +00:00
"${dawn_shaderc_dir}:spirv_cross",
Validate SPIR-V code when creating ShaderModules This integrates spirv-val in dawn_native so that regular and WebGPU-specific validation of shaders is done. Also adds tests to check OpUndef is correctly rejected so we know WebGPU-specific validation is working. Change-Id: If49d276c98bca8cd3c6c1a420903fe34923a2942
2018-09-06 15:25:46 +00:00
"${dawn_spirv_tools_dir}:spvtools_val",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
Convert spvc build flag to a runtime toggle Also moves some of the spirv_cross code into the main library that was feature guarded, since spvc requires it. BUG=dawn:281 Change-Id: I482d1d5a5c851956d3815bad90665c52a1ea15bb Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13860 Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-11-21 18:08:15 +00:00
defines = []
Allow using swiftshader with the Vulkan backend This adds swiftshader as a dependency of Dawn, and when it is present dawn_use_swiftshader=true will force usage of it. (due to a Vulkan loader limitation we can't have both regular drivers and swiftshader in the same VkInstance). BUG=dawn:283 Change-Id: Ib94f4dcca652eb380e994f007cdcfb145b1a5102 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13440 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-11-26 18:21:51 +00:00
libs = []
data_deps = []
Revert "Convert spvc build flag to a runtime toggle" This reverts commit 1954436fe28557dab8381f5b0f8ca7d68ab091c8. Reason for revert: The shaderc side of this multi-patch brings in a dependency on glslang, which uses a static initializer, which chromium doesn't like. Original change's description: > Convert spvc build flag to a runtime toggle > > Also moves some of the spirv_cross code into the main library that was > feature guarded, since spvc requires it. > > BUG=dawn:281 > > Change-Id: I482d1d5a5c851956d3815bad90665c52a1ea15bb > Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13860 > Reviewed-by: Corentin Wallez <cwallez@chromium.org> TBR=cwallez@chromium.org,kainino@chromium.org,enga@chromium.org,rharrison@chromium.org Change-Id: Ia9a025fb4440c96874d1b45776a9f97023ca591d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: dawn:281 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13941 Reviewed-by: Ryan Harrison <rharrison@chromium.org> Commit-Queue: Ryan Harrison <rharrison@chromium.org>
2019-11-21 20:31:05 +00:00
Don't use shared libraries in the wire fuzzer. Otherwise UBSan complains that C++ types are different between the shared libraries because libc++ is linked statically. BUG=chromium:904736 Change-Id: I51ef40d1f7910fd693a4585c74ff404812472d2e Reviewed-on: https://dawn-review.googlesource.com/c/2380 Reviewed-by: Dan Sinclair <dsinclair@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2018-11-14 21:04:26 +00:00
configs += [ ":libdawn_native_internal" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
Fix compilation of the OpenGL backend on Mac OpenGLBackend.cpp would end up including KHR/khrplatform.h when the libdawn_native target that contains it doesn't have a dependency on the khr_platform target. Fix this by making libdawn_native_sources expose some of its dependencies as public_deps. BUG= Change-Id: I45c05a064e4b73ab7ac6f5f6258e7983e5fc085d Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9205 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org>
2019-07-22 23:32:29 +00:00
# Dependencies that are needed to compile libdawn_native entry points in
# FooBackend.cpp need to be public deps so they are propagated to the
# libdawn_native target
Add dawn_platform::Platform for handling tracing events in Dawn This patch provides Chromium TRACE_EVENT macros and hooks for implementing the TRACE_EVENT api. Bug: chromium:958013 Change-Id: I033b1c7ca57c550504a1bea1898a1a152831922b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7060 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-13 19:00:34 +00:00
public_deps = [
":dawn_platform",
Refactor code to have rudimentary support for using SPVC This is the first step for having a fully operational SPVC usage path. This version of SPVC integration uses SPVC for setting up the options to the compiler, but a lot of the actual interaction with spirv-cross is done in Dawn, just via SPVC's compiler object. Future CLs will migrate more of the spirv-cross interaction to using the SPVC API, eventually removing the need for Dawn to know about spirv-cross. BUG=dawn:288 Change-Id: I68e0773f910d7fe967235b6987b3debe1d13883f Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/14143 Commit-Queue: Ryan Harrison <rharrison@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-12-03 20:25:13 +00:00
"${dawn_shaderc_dir}:libshaderc_spvc",
Add dawn_platform::Platform for handling tracing events in Dawn This patch provides Chromium TRACE_EVENT macros and hooks for implementing the TRACE_EVENT api. Bug: chromium:958013 Change-Id: I033b1c7ca57c550504a1bea1898a1a152831922b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7060 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-13 19:00:34 +00:00
]
Fix compilation of the OpenGL backend on Mac OpenGLBackend.cpp would end up including KHR/khrplatform.h when the libdawn_native target that contains it doesn't have a dependency on the khr_platform target. Fix this by making libdawn_native_sources expose some of its dependencies as public_deps. BUG= Change-Id: I45c05a064e4b73ab7ac6f5f6258e7983e5fc085d Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9205 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org>
2019-07-22 23:32:29 +00:00
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
sources = get_target_outputs(":libdawn_native_utils_gen")
sources += [
dawn_native: Add Instance and Adapters New objects are introduced to control what happens before device creation in dawn_native: - Instance: a connection from the application to dawn_native that is used for dependency injection and to discover adapters. - Adapters: represents the possibility of device creation for a specific (GPU, backend) pair. - BackendConnection: an internal object that standardizes the interface between the frontend and backends. The BackendConnection interface is implemented for the Null backend and stubbed out in other backends. This allows this change to port the ValidationTests to use the new Instance and Adapters concept and deal with other backends later. BUG=dawn:29 Change-Id: I19719a9342b4af091accc0c02fb6b9697eadde7b Reviewed-on: https://dawn-review.googlesource.com/c/3500 Reviewed-by: Stephen White <senorblanco@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-04 10:30:40 +00:00
"src/dawn_native/Adapter.cpp",
"src/dawn_native/Adapter.h",
Deduplicate AttachmentState shared by RenderPipeline and RenderPasses This both deduplicates shared state by multiple passes or pipelines and makes checking pipeline compatibility a single pointer check. It will be useful for also checking RenderBundle compatibility. Bug: dawn:154 Change-Id: I0fb289fab5ac76a7fbd500f64b8a6409a246ab32 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9461 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-07-26 19:08:18 +00:00
"src/dawn_native/AttachmentState.cpp",
"src/dawn_native/AttachmentState.h",
dawn_native: Add Instance and Adapters New objects are introduced to control what happens before device creation in dawn_native: - Instance: a connection from the application to dawn_native that is used for dependency injection and to discover adapters. - Adapters: represents the possibility of device creation for a specific (GPU, backend) pair. - BackendConnection: an internal object that standardizes the interface between the frontend and backends. The BackendConnection interface is implemented for the Null backend and stubbed out in other backends. This allows this change to port the ValidationTests to use the new Instance and Adapters concept and deal with other backends later. BUG=dawn:29 Change-Id: I19719a9342b4af091accc0c02fb6b9697eadde7b Reviewed-on: https://dawn-review.googlesource.com/c/3500 Reviewed-by: Stephen White <senorblanco@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-04 10:30:40 +00:00
"src/dawn_native/BackendConnection.cpp",
"src/dawn_native/BackendConnection.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/BindGroup.cpp",
"src/dawn_native/BindGroup.h",
"src/dawn_native/BindGroupLayout.cpp",
"src/dawn_native/BindGroupLayout.h",
Support setting bind groups before pipeline for all backends This is to match WebGPU semantics. Bug: dawn:201 Change-Id: I2aab671fc389edf1d2765395814a9c831afc653e Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11080 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-09-17 19:25:27 +00:00
"src/dawn_native/BindGroupTracker.h",
Resource Management 3: Buddy allocator Introduces the buddy system for fast power-of-two sub-allocation. BUG=dawn:27 Change-Id: I56836ae317ecc5a91d8341c843fc37d4f91fb5af Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9260 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-07-30 16:46:10 +00:00
"src/dawn_native/BuddyAllocator.cpp",
"src/dawn_native/BuddyAllocator.h",
Resource Management 7: Device memory sub-allocation using buddy allocator. Uses a large buddy system to allocate binary sized heaps on-demand. BUG=dawn:27 Change-Id: I72e425c23e601da6ee53827423bef7ff13be049c Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/10880 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com>
2019-10-03 18:17:31 +00:00
"src/dawn_native/BuddyMemoryAllocator.cpp",
"src/dawn_native/BuddyMemoryAllocator.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/Buffer.cpp",
"src/dawn_native/Buffer.h",
Only mark objects as cached right before inserting into the cache This fixes bugs where we try to uncache objects that fail creation. Bug: dawn:249 Change-Id: Ic60b3ce702dfdda18baa6d263911885a43d3cda7 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12820 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-10-30 00:20:03 +00:00
"src/dawn_native/CachedObject.cpp",
"src/dawn_native/CachedObject.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/CommandAllocator.cpp",
"src/dawn_native/CommandAllocator.h",
"src/dawn_native/CommandBuffer.cpp",
"src/dawn_native/CommandBuffer.h",
"src/dawn_native/CommandBufferStateTracker.cpp",
"src/dawn_native/CommandBufferStateTracker.h",
WebGPU error handling 2: CommandEncoder for samples and end2end tests CommandEncoder is the replacement for CommandBufferBuilder. This commit adds the dawn.json definition for it and an initial implementation that wraps CommandBufferBuilder. This is done so that the code can be ported to CommandEncoder gradually, otherwise the commit would be too big and would risk many merge conflicts. This converts all samples and end2end tests to use CommandEncoder. BUG=dawn:8 Change-Id: If4ce86e6fb39ba4e0c2af6328d40e63be17d18c1 Reviewed-on: https://dawn-review.googlesource.com/c/4741 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-02-15 12:54:08 +00:00
"src/dawn_native/CommandEncoder.cpp",
"src/dawn_native/CommandEncoder.h",
Factor RenderPass command validation Validation of GPURenderBundle will share code with RenderPass validation. Factor validation of commands for GPURenderBundle into a separate function. Bug: dawn:154 Change-Id: I79a229592ead27d462da0dd2d12fbdb95443ff19 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9980 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-13 00:22:28 +00:00
"src/dawn_native/CommandValidation.cpp",
"src/dawn_native/CommandValidation.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/Commands.cpp",
"src/dawn_native/Commands.h",
Introduce [Render|Compute]PassEncoder. This splits off part of CommandBufferBuilder in separate RenderPassEncoder and ComputePassEncoder objects. To match the WebGPU IDL and factor some code, both these encoders inherit from ProgrammablePassEncoder. These encoders are pure frontend objects and record into the CommandBufferBuilder command allocator objects, so no changes to the backends were needed. Error handling is still ew, because the "builder" mechanism we had doesn't allow for "split builders". Nicer error handling will have to wait on Dawn matching WebGPU. All the tests and samples were updated to the new structure. BUG=dawn:5 Change-Id: I5f5d4ad866e2c07fedd1ba7a122258c6610941f1 Reviewed-on: https://dawn-review.googlesource.com/1543 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2018-09-21 00:24:37 +00:00
"src/dawn_native/ComputePassEncoder.cpp",
"src/dawn_native/ComputePassEncoder.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/ComputePipeline.cpp",
"src/dawn_native/ComputePipeline.h",
"src/dawn_native/Device.cpp",
"src/dawn_native/Device.h",
Memory manager: buffer uploads (D3D) - Part 1 Manages a single persistently mapped GPU heap which is sub-allocated inside of ring-buffer for uploads. To handle larger buffers without additional unused heaps, ring buffers are created on-demand. BUG=dawn:28 TEST=dawn_unittests Change-Id: Ifc5a1b06baf8633f1e133245ac1ee76275431cc5 Reviewed-on: https://dawn-review.googlesource.com/c/3160 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-29 00:10:07 +00:00
"src/dawn_native/DynamicUploader.cpp",
"src/dawn_native/DynamicUploader.h",
Factor EncodingContext out of CommandEncoderBase. This patch factors the CommandAllocator, CommandIterator, and error handling out of CommandEncoderBase so it can later be used by the RenderBundleEncoder. Bug: dawn:154 Change-Id: Ia4f8c3ce7f432f0887b619bd8090aa9bec7330fc Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9181 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-07-24 18:15:24 +00:00
"src/dawn_native/EncodingContext.cpp",
"src/dawn_native/EncodingContext.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/Error.h",
"src/dawn_native/ErrorData.cpp",
"src/dawn_native/ErrorData.h",
fuzzing: Add error injection macros to the Vulkan backend This will enable fuzzing the Vulkan backend with randomly injected errors to help ensure the backend properly handles all errors. It also redefines VkResult in the dawn_native::vulkan namespace such that a VkResult cannot be used unless it is explicitly wrapped. Bug: dawn:295 Change-Id: I3ab2f98702a67a61afe06315658a9ab76ed4ccc3 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/14520 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-12-17 00:47:40 +00:00
"src/dawn_native/ErrorInjector.cpp",
"src/dawn_native/ErrorInjector.h",
Implement ErrorScopes for synchronous errors This patch implements Push/PopErrorScope except for asynchronous or GPU commands. These commands, such as Queue::Submit will need to hold onto the ErrorScope until GPU execution is complete. Bug: dawn:153 Change-Id: I2d340b8b391d117a59497f35690993a9cd7503e6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/10700 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-09-10 23:19:11 +00:00
"src/dawn_native/ErrorScope.cpp",
"src/dawn_native/ErrorScope.h",
Support ErrorScopes for asynchronous GPU execution This changes updates ErrorScopes so that scopes enclosing a Queue::Submit or Queue::Signal resolve their callbacks asynchronously after GPU execution is complete. Bug: dawn:153 Change-Id: I0e0b8a9f19f3f29d1b6a3683938154b87f190a07 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/10701 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-09-17 18:24:07 +00:00
"src/dawn_native/ErrorScopeTracker.cpp",
"src/dawn_native/ErrorScopeTracker.h",
Support BC formats as the first extension in Dawn This patch refactors the current implementation of BC formats to treat it as the first extension in Dawn and adds all the related tests. Note that in Dawn all the extensions are disabled unless we enable them when we create the device, which means the BC formats can only be used when we enable the related extension on the creation of the device, and the creation of the device will fail if the adapter does not support the extension BUG=dawn:42 TEST=dawn_end2end_tests TEST=dawn_unittests Change-Id: I04d818b0218ebb3b1b7a70a4fea71779f308f85f Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9520 Commit-Queue: Jiawei Shao <jiawei.shao@intel.com> Reviewed-by: Austin Eng <enga@chromium.org>
2019-08-02 00:06:38 +00:00
"src/dawn_native/Extensions.cpp",
"src/dawn_native/Extensions.h",
Implement timeline fences in Dawn This change implements timeline fences in Dawn. It includes methods and descriptor members to eventually support multi-queue, but does not implement them. Bug: dawn:26 Change-Id: I81d5fee6acef402fe099227a034d9669a89ab6c3 Reviewed-on: https://dawn-review.googlesource.com/c/2460 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2018-12-03 16:57:34 +00:00
"src/dawn_native/Fence.cpp",
"src/dawn_native/Fence.h",
"src/dawn_native/FenceSignalTracker.cpp",
"src/dawn_native/FenceSignalTracker.h",
Precompute all the Formats at Device creation in the FormatTable This is needed for two reasons: - TextureBase and TextureViewBase stored Formats by value which isn't too much overhead at this time but will get bigger in the future. - The OpenGL backends needs its own GLFormat structure to store data about each format which will eventually contain complicated logic to detect support in the GL driver so it shouldn't be duplicated in Textures. The computations of the information about Format is moved from being done whenever they are needed to being precomputed at DeviceBase initialization. This makes each format have a constant "index" in that can be used in the backends to address their own structure, for example a GLFormat table. Also some DeviceBase pointers were made const for validation. BUG=dawn:128 Change-Id: I37d1e9c739b87cddcea09cb1759e175704d90f9e Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9101 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Jiawei Shao <jiawei.shao@intel.com> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-07-18 09:25:04 +00:00
"src/dawn_native/Format.cpp",
"src/dawn_native/Format.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/Forward.h",
dawn_native: Add Instance and Adapters New objects are introduced to control what happens before device creation in dawn_native: - Instance: a connection from the application to dawn_native that is used for dependency injection and to discover adapters. - Adapters: represents the possibility of device creation for a specific (GPU, backend) pair. - BackendConnection: an internal object that standardizes the interface between the frontend and backends. The BackendConnection interface is implemented for the Null backend and stubbed out in other backends. This allows this change to port the ValidationTests to use the new Instance and Adapters concept and deal with other backends later. BUG=dawn:29 Change-Id: I19719a9342b4af091accc0c02fb6b9697eadde7b Reviewed-on: https://dawn-review.googlesource.com/c/3500 Reviewed-by: Stephen White <senorblanco@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-04 10:30:40 +00:00
"src/dawn_native/Instance.cpp",
"src/dawn_native/Instance.h",
Put the reference to DeviceBase in a new ObjectBase ObjectBase will contain data that all WebGPU objects have such as a pointer back to the device, a refcount (via inheriting from RefCounted), a name, an error status etc. BUG=dawn:24 Change-Id: I919e1a6d4a68811ceb6e503b2a793815c92f2528 Reviewed-on: https://dawn-review.googlesource.com/c/1620 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2018-10-15 12:54:30 +00:00
"src/dawn_native/ObjectBase.cpp",
"src/dawn_native/ObjectBase.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/PassResourceUsage.h",
Factor PassResourceUsageTracker to its own file GPURenderBundleEncoder and GPUCommandEncoder will need to share code for tracking resource usages. Bug: dawn:154 Change-Id: I0286f71c4c0638f89be2754c8e9691e67e5db335 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9700 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-08 17:21:39 +00:00
"src/dawn_native/PassResourceUsageTracker.cpp",
"src/dawn_native/PassResourceUsageTracker.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/PerStage.cpp",
"src/dawn_native/PerStage.h",
"src/dawn_native/Pipeline.cpp",
"src/dawn_native/Pipeline.h",
"src/dawn_native/PipelineLayout.cpp",
"src/dawn_native/PipelineLayout.h",
Introduce [Render|Compute]PassEncoder. This splits off part of CommandBufferBuilder in separate RenderPassEncoder and ComputePassEncoder objects. To match the WebGPU IDL and factor some code, both these encoders inherit from ProgrammablePassEncoder. These encoders are pure frontend objects and record into the CommandBufferBuilder command allocator objects, so no changes to the backends were needed. Error handling is still ew, because the "builder" mechanism we had doesn't allow for "split builders". Nicer error handling will have to wait on Dawn matching WebGPU. All the tests and samples were updated to the new structure. BUG=dawn:5 Change-Id: I5f5d4ad866e2c07fedd1ba7a122258c6610941f1 Reviewed-on: https://dawn-review.googlesource.com/1543 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2018-09-21 00:24:37 +00:00
"src/dawn_native/ProgrammablePassEncoder.cpp",
"src/dawn_native/ProgrammablePassEncoder.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/Queue.cpp",
"src/dawn_native/Queue.h",
"src/dawn_native/RefCounted.cpp",
"src/dawn_native/RefCounted.h",
Implement RenderBundle in the frontend This CL implements RenderBundle and RenderBundleEncoder in the frontend and adds unittests for validation. Bug: dawn:154 Change-Id: Ice5ecd384cd627ad270b73052408f8139d1ea5f4 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9221 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-13 22:12:54 +00:00
"src/dawn_native/RenderBundle.cpp",
"src/dawn_native/RenderBundle.h",
"src/dawn_native/RenderBundleEncoder.cpp",
"src/dawn_native/RenderBundleEncoder.h",
Add RenderEncoderBase to match WebGPU class hierarchy. This is needed so that RenderBundleEncoder and RenderPassEncoder can share code. This patch also moves EndPass out of ProgrammablePassEncoder and into both RenderPassEncoder and ComputePassEncoder. Render bundles do not have EndPass. Bug: dawn:154 Change-Id: Ib7126b2ba718b0b93e3d6f15c429ac910c0d5d31 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9180 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-07-20 01:34:56 +00:00
"src/dawn_native/RenderEncoderBase.cpp",
"src/dawn_native/RenderEncoderBase.h",
Introduce [Render|Compute]PassEncoder. This splits off part of CommandBufferBuilder in separate RenderPassEncoder and ComputePassEncoder objects. To match the WebGPU IDL and factor some code, both these encoders inherit from ProgrammablePassEncoder. These encoders are pure frontend objects and record into the CommandBufferBuilder command allocator objects, so no changes to the backends were needed. Error handling is still ew, because the "builder" mechanism we had doesn't allow for "split builders". Nicer error handling will have to wait on Dawn matching WebGPU. All the tests and samples were updated to the new structure. BUG=dawn:5 Change-Id: I5f5d4ad866e2c07fedd1ba7a122258c6610941f1 Reviewed-on: https://dawn-review.googlesource.com/1543 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2018-09-21 00:24:37 +00:00
"src/dawn_native/RenderPassEncoder.cpp",
"src/dawn_native/RenderPassEncoder.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/RenderPipeline.cpp",
"src/dawn_native/RenderPipeline.h",
Resource Management 5: D3D support for resource allocation. Refactor existing resource allocators by adding a memory type and memory handle. BUG=dawn:27, dawn:153 Change-Id: I090b6ab40e7eaa0d7ea5ce1e8b760e961be9b559 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9420 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-27 23:36:26 +00:00
"src/dawn_native/ResourceHeap.h",
Preliminary changes to Vulkan memory suballocation This mostly makes the MemoryAllocator not owned by the BuddyResourceAllocator so that we don't need an extra class for the dependency injection in the Vulkan backend. (the container for the BuddyMemoryAllocator can be it's MemoryAllocator at the same time). Also renames methods of MemoryAllocator to be more explicit. Also renames the constructor parameter of BuddyMemoryAllocator to be (subjectively) closer to what the represent. BUG=dawn:27 Change-Id: I37355ad5b3cded143956f0adc4742fa1b717e9bc Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12661 Reviewed-by: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-10-24 21:28:16 +00:00
"src/dawn_native/ResourceHeapAllocator.h",
Resource Management 5: D3D support for resource allocation. Refactor existing resource allocators by adding a memory type and memory handle. BUG=dawn:27, dawn:153 Change-Id: I090b6ab40e7eaa0d7ea5ce1e8b760e961be9b559 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9420 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-27 23:36:26 +00:00
"src/dawn_native/ResourceMemoryAllocation.cpp",
"src/dawn_native/ResourceMemoryAllocation.h",
Remove device dependencies from ringbuffer. Allows ringbuffer sub-allocator to be used for non-staging memory. BUG=dawn:155 Change-Id: Id0021907f520909aaebaf79e992124a47797d38d Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9760 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com>
2019-09-18 22:06:41 +00:00
"src/dawn_native/RingBufferAllocator.cpp",
"src/dawn_native/RingBufferAllocator.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/Sampler.cpp",
"src/dawn_native/Sampler.h",
"src/dawn_native/ShaderModule.cpp",
"src/dawn_native/ShaderModule.h",
Memory manager: buffer uploads (D3D) - Part 1 Manages a single persistently mapped GPU heap which is sub-allocated inside of ring-buffer for uploads. To handle larger buffers without additional unused heaps, ring buffers are created on-demand. BUG=dawn:28 TEST=dawn_unittests Change-Id: Ifc5a1b06baf8633f1e133245ac1ee76275431cc5 Reviewed-on: https://dawn-review.googlesource.com/c/3160 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-29 00:10:07 +00:00
"src/dawn_native/StagingBuffer.cpp",
"src/dawn_native/StagingBuffer.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/SwapChain.cpp",
"src/dawn_native/SwapChain.h",
"src/dawn_native/Texture.cpp",
"src/dawn_native/Texture.h",
"src/dawn_native/ToBackend.h",
Move all the implementations of Toggle to Toggles.cpp This patch moves all the code related to Toggle from Instance.cpp to Toggles.cpp to make the code in Instance.cpp cleaner. BUG=dawn:56 Change-Id: Ica2a779569478a58ddf21e632a211c0c5b889b00 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9580 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Jiawei Shao <jiawei.shao@intel.com>
2019-07-30 23:58:52 +00:00
"src/dawn_native/Toggles.cpp",
Emulate store and multisample resolve on Metal This patch implements "store and MSAA resolve" store operation on Metal drivers that don't support MTLStoreActionStoreAndMultisampleResolve with a workaround that does MSAA resolve in another render pass. Driver workaround is one type of Dawn Toggles. Dawn Toggles will include other optional optimizations and features that can be configured to use or not when we create Dawn Devices. As all Metal try bots don't need this toggle, to better test this patch on the try bots: 1. We add the support of forcing enabling a workaround when starting an Dawn end2end test so that we can test the workaround on the platforms where the workaround is disabled. 2. We add an optional parameter DeviceDescriptor to CreateDevice() so that we can custom the toggles the Dawn device should use. This patch also adds the support of querying toggle details from Instance and the names of the toggles in use from Device. These APIs are tested in the Dawn unittests added in this patch. BUG=dawn:56 TEST=dawn_end2end_tests TEST=dawn_unittests Change-Id: Iae31d2ded6057eee638b6099d3061e9d78b04d55 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/6620 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Jiawei Shao <jiawei.shao@intel.com>
2019-04-26 07:52:57 +00:00
"src/dawn_native/Toggles.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/dawn_platform.h",
]
if (dawn_enable_d3d12) {
D3D12: Dynamically load D3D12, DXGI and D3DCompiler Linking against their .lib makes loading Dawn fail on systems that don't have the DLLs. This happens for example on Windows7 that doesn't have d3d12.dll. Instead we dynamically load functions pointers from these DLLs at d3d12::Device startup. Change-Id: I4d01a12d0f91bec45bf125450d2c08aaa9ff9fac
2018-08-30 12:20:28 +00:00
libs += [ "dxguid.lib" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
sources += [
D3D12: Implement the backend connection and adapter. BUG=dawn:29 Change-Id: Id4497b4a91ba58b79d1cd976a52df5a0fa5d60a8 Reviewed-on: https://dawn-review.googlesource.com/c/3844 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-30 16:07:48 +00:00
"src/dawn_native/d3d12/AdapterD3D12.cpp",
"src/dawn_native/d3d12/AdapterD3D12.h",
"src/dawn_native/d3d12/BackendD3D12.cpp",
"src/dawn_native/d3d12/BackendD3D12.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/BindGroupD3D12.cpp",
"src/dawn_native/d3d12/BindGroupD3D12.h",
"src/dawn_native/d3d12/BindGroupLayoutD3D12.cpp",
"src/dawn_native/d3d12/BindGroupLayoutD3D12.h",
"src/dawn_native/d3d12/BufferD3D12.cpp",
"src/dawn_native/d3d12/BufferD3D12.h",
"src/dawn_native/d3d12/CommandAllocatorManager.cpp",
"src/dawn_native/d3d12/CommandAllocatorManager.h",
"src/dawn_native/d3d12/CommandBufferD3D12.cpp",
"src/dawn_native/d3d12/CommandBufferD3D12.h",
Add CommandRecordingContext to D3D12 This change refactors D3D12 backend to have CommandRecordingContext CommandRecordingContext allows us to, in a future, add additional data to the context such as textures that need to be acquired and released before command lists are executed. The Device's pending command list and the command list which resides in the Queue object were converted to use CommandRecordingContext. Bug=dawn:234 Change-Id: Ic13a229fc1f15895ef71117ce638c942de224743 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11940 Commit-Queue: Rafael Cintron <rafael.cintron@microsoft.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-10-10 18:06:58 +00:00
"src/dawn_native/d3d12/CommandRecordingContext.cpp",
"src/dawn_native/d3d12/CommandRecordingContext.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/ComputePipelineD3D12.cpp",
"src/dawn_native/d3d12/ComputePipelineD3D12.h",
D3D12 replace ASSERT_SUCCESS with better error handling Added D3D12Error to check HRESULTS and return error messages with the correct error names. Remove ASSERT_SUCCESS from D3D12 backend and use MaybeError and ResultError instead to handle errors. Bug: dawn:19 Change-Id: Idf2f1987725e7e658bd29a9b13653125ab43c564 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12000 Reviewed-by: Rafael Cintron <rafael.cintron@microsoft.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-10-16 09:26:54 +00:00
"src/dawn_native/d3d12/D3D12Error.cpp",
"src/dawn_native/d3d12/D3D12Error.h",
Improve D3D12 adapter initialization. Gather device info at device initialization rather than adapter initialization. BUG=dawn:144 Change-Id: I07e114731a37f3738daa585afa99675f2fd36289 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7700 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-06-12 18:54:57 +00:00
"src/dawn_native/d3d12/D3D12Info.cpp",
"src/dawn_native/d3d12/D3D12Info.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/DescriptorHeapAllocator.cpp",
"src/dawn_native/d3d12/DescriptorHeapAllocator.h",
"src/dawn_native/d3d12/DeviceD3D12.cpp",
"src/dawn_native/d3d12/DeviceD3D12.h",
"src/dawn_native/d3d12/Forward.h",
Resource Management 8: placed resource sub-allocation. - Adds d3d allocators (placed resource + heap). - Support for heap tier 1 but only buffers. - Suballocation optimization is enabled for allocations under 4MB. BUG=dawn:27 Change-Id: I79177830670d1f322bbadf45f797415a3e9208d9 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5680 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com>
2019-10-17 17:25:28 +00:00
"src/dawn_native/d3d12/HeapAllocatorD3D12.cpp",
"src/dawn_native/d3d12/HeapAllocatorD3D12.h",
"src/dawn_native/d3d12/HeapD3D12.cpp",
"src/dawn_native/d3d12/HeapD3D12.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/NativeSwapChainImplD3D12.cpp",
"src/dawn_native/d3d12/NativeSwapChainImplD3D12.h",
"src/dawn_native/d3d12/PipelineLayoutD3D12.cpp",
"src/dawn_native/d3d12/PipelineLayoutD3D12.h",
D3D12: Dynamically load D3D12, DXGI and D3DCompiler Linking against their .lib makes loading Dawn fail on systems that don't have the DLLs. This happens for example on Windows7 that doesn't have d3d12.dll. Instead we dynamically load functions pointers from these DLLs at d3d12::Device startup. Change-Id: I4d01a12d0f91bec45bf125450d2c08aaa9ff9fac
2018-08-30 12:20:28 +00:00
"src/dawn_native/d3d12/PlatformFunctions.cpp",
"src/dawn_native/d3d12/PlatformFunctions.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/QueueD3D12.cpp",
"src/dawn_native/d3d12/QueueD3D12.h",
Implement D3D12 Native Render Passes Uses D3D12 native render pass API when possible. On pre-RS5 builds of Windows, Dawn will fall back to a software emulated render pass. A toggle was added to provide test coverage to the emulated render pass implementation and used in tests that test render pass functionality in particular. Bug: dawn:36 Change-Id: I297a3ec7655b68d28204db2d3ab78cb82bb4e7a5 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13082 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Brandon Jones <brandon1.jones@intel.com>
2019-11-12 18:14:21 +00:00
"src/dawn_native/d3d12/RenderPassBuilderD3D12.cpp",
"src/dawn_native/d3d12/RenderPassBuilderD3D12.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/RenderPipelineD3D12.cpp",
"src/dawn_native/d3d12/RenderPipelineD3D12.h",
D3D12: Move resource allocators from device into manager. Encapsulates resource allocation using a manager class. BUG=dawn:27 Change-Id: I7a496261dcede647d32e44d96ed27237bf418fb2 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11742 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com>
2019-10-02 21:45:09 +00:00
"src/dawn_native/d3d12/ResourceAllocatorManagerD3D12.cpp",
"src/dawn_native/d3d12/ResourceAllocatorManagerD3D12.h",
D3D12: Move resource into allocation handle. Allows buffer/texture direct access to underlying resource rather than indirectly with a opaque memory type. BUG=dawn:27 Change-Id: I2eb69f4e30c96c431dbc96094d671be1e0a29869 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11800 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com>
2019-10-09 16:50:42 +00:00
"src/dawn_native/d3d12/ResourceHeapAllocationD3D12.cpp",
"src/dawn_native/d3d12/ResourceHeapAllocationD3D12.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/SamplerD3D12.cpp",
"src/dawn_native/d3d12/SamplerD3D12.h",
"src/dawn_native/d3d12/ShaderModuleD3D12.cpp",
"src/dawn_native/d3d12/ShaderModuleD3D12.h",
Memory manager: buffer uploads (D3D) - Part 1 Manages a single persistently mapped GPU heap which is sub-allocated inside of ring-buffer for uploads. To handle larger buffers without additional unused heaps, ring buffers are created on-demand. BUG=dawn:28 TEST=dawn_unittests Change-Id: Ifc5a1b06baf8633f1e133245ac1ee76275431cc5 Reviewed-on: https://dawn-review.googlesource.com/c/3160 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-29 00:10:07 +00:00
"src/dawn_native/d3d12/StagingBufferD3D12.cpp",
"src/dawn_native/d3d12/StagingBufferD3D12.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/SwapChainD3D12.cpp",
"src/dawn_native/d3d12/SwapChainD3D12.h",
"src/dawn_native/d3d12/TextureCopySplitter.cpp",
"src/dawn_native/d3d12/TextureCopySplitter.h",
"src/dawn_native/d3d12/TextureD3D12.cpp",
"src/dawn_native/d3d12/TextureD3D12.h",
Complete the sampler object to match WebGPU WebGPUSampler is much more complete than Dawn's Sampler. This patch implement the missing part. BUG=dawn:47 Change-Id: Ief45cb9710493e9d79ddab60fe3be5a123b76ebd Reviewed-on: https://dawn-review.googlesource.com/c/3540 Commit-Queue: Shaobo Yan <shaobo.yan@intel.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-04 04:56:08 +00:00
"src/dawn_native/d3d12/UtilsD3D12.cpp",
"src/dawn_native/d3d12/UtilsD3D12.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/d3d12/d3d12_platform.h",
]
}
if (dawn_enable_metal) {
libs += [
"Cocoa.framework",
Collect device information on Metal Becuase CGDisplayIOServicePort is deprecated in OSX >= 10.9, we create an alternative function which manually finding a service port with matching vendor and product IDs. BUG=dawn:10 TEST=dawn_end2end_tests Change-Id: I94ff65911e159c2b7075209d8902c1551560ed47 Reviewed-on: https://dawn-review.googlesource.com/c/2541 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2018-11-29 10:54:03 +00:00
"IOKit.framework",
Implement wrapping IOSurfaces in dawn::Texture. This allows wrapping IOSurfaces in a dawn::Texture so a Dawn application can sample from, or render to an IOSurface. It uses Metal's functionality for wrapping textures in MTLTexture. Support for single-plane BGRA8, RG8 and R8 IOSurfaces is added as well as tests for sampling and using BeginRenderPass to clear them. BUG=dawn:112 Change-Id: I367dbd1a75a0c7b81901fb0aae05f1cd46af3f3a Reviewed-on: https://dawn-review.googlesource.com/c/5101 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-03-01 12:01:18 +00:00
"IOSurface.framework",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
sources += [
Metal: Implement the backend connection and adapter. BUG=dawn:29 Change-Id: Idaca7d2f8ac52d5f46d8030571b5e2da3a573a97 Reviewed-on: https://dawn-review.googlesource.com/c/3940 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-02-05 13:02:30 +00:00
"src/dawn_native/metal/BackendMTL.h",
"src/dawn_native/metal/BackendMTL.mm",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/metal/BufferMTL.h",
"src/dawn_native/metal/BufferMTL.mm",
"src/dawn_native/metal/CommandBufferMTL.h",
"src/dawn_native/metal/CommandBufferMTL.mm",
"src/dawn_native/metal/ComputePipelineMTL.h",
"src/dawn_native/metal/ComputePipelineMTL.mm",
"src/dawn_native/metal/DeviceMTL.h",
"src/dawn_native/metal/DeviceMTL.mm",
"src/dawn_native/metal/Forward.h",
"src/dawn_native/metal/PipelineLayoutMTL.h",
"src/dawn_native/metal/PipelineLayoutMTL.mm",
"src/dawn_native/metal/QueueMTL.h",
"src/dawn_native/metal/QueueMTL.mm",
"src/dawn_native/metal/RenderPipelineMTL.h",
"src/dawn_native/metal/RenderPipelineMTL.mm",
"src/dawn_native/metal/SamplerMTL.h",
"src/dawn_native/metal/SamplerMTL.mm",
"src/dawn_native/metal/ShaderModuleMTL.h",
"src/dawn_native/metal/ShaderModuleMTL.mm",
Memory manager: buffer uploads (Metal+refactor) - Part 3 Manages a single persistently mapped GPU heap which is sub-allocated inside of ring-buffer for uploads. To handle larger buffers without additional unused heaps, ring buffers are created on-demand. BUG=dawn:28 TEST=dawn_unittests Change-Id: If4d3e717186895b1409502c1dea5ab751a4776b2 Reviewed-on: https://dawn-review.googlesource.com/c/4440 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com>
2019-02-15 21:18:40 +00:00
"src/dawn_native/metal/StagingBufferMTL.h",
"src/dawn_native/metal/StagingBufferMTL.mm",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/metal/SwapChainMTL.h",
"src/dawn_native/metal/SwapChainMTL.mm",
"src/dawn_native/metal/TextureMTL.h",
"src/dawn_native/metal/TextureMTL.mm",
Complete the sampler object to match WebGPU WebGPUSampler is much more complete than Dawn's Sampler. This patch implement the missing part. BUG=dawn:47 Change-Id: Ief45cb9710493e9d79ddab60fe3be5a123b76ebd Reviewed-on: https://dawn-review.googlesource.com/c/3540 Commit-Queue: Shaobo Yan <shaobo.yan@intel.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-04 04:56:08 +00:00
"src/dawn_native/metal/UtilsMetal.h",
"src/dawn_native/metal/UtilsMetal.mm",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
}
if (dawn_enable_null) {
sources += [
dawn_native: define exported functions in their own files. This adds a new FooBackend.cpp file for each backend that defines exactly the symbols that are exported by libdawn_native's headers. THis will allow factoring most of the compilation of dawn_native between the shared and static library variants. BUG=dawn:85 Change-Id: I69c808dac2fe5e8bb08356117e3997677787b08a Reviewed-on: https://dawn-review.googlesource.com/c/3760 Reviewed-by: Stephen White <senorblanco@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 08:35:16 +00:00
"src/dawn_native/null/DeviceNull.cpp",
"src/dawn_native/null/DeviceNull.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
}
if (dawn_enable_opengl) {
Fix compilation of the OpenGL backend on Mac OpenGLBackend.cpp would end up including KHR/khrplatform.h when the libdawn_native target that contains it doesn't have a dependency on the khr_platform target. Fix this by making libdawn_native_sources expose some of its dependencies as public_deps. BUG= Change-Id: I45c05a064e4b73ab7ac6f5f6258e7983e5fc085d Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9205 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org>
2019-07-22 23:32:29 +00:00
public_deps += [
OpenGL: Don't use glad to load OpenGL entrypoints This makes the OpenGL entry points loaded at Adapter creation from the getProcAddress passed in the DiscoveryOptions and update all GL calls in the backend to go through the new OpenGLFunctions object. A code generator is added that generates the function loader and list of GL procs from Khronos' gl.xml file but we can't get rid of glad yet because it is used to have the PROC typedefs and enum values. BUG=dawn:165 Change-Id: I2a583d79752f55877fa4190846f5be16cf91651a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7983 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-13 10:22:32 +00:00
":libdawn_native_opengl_loader_gen",
Remove glad and replace it with our own GL header This completely removes the dependency on glad by generating the GL headers from gl.xml directly. This requires adding khrplatform.h so all Khronos dependencies are gathered in third_party/khronos. Also removes a stray CMakeLists.txt that was still hanging out. BUG=dawn:165 Change-Id: Ia64bc51bc8b18c6b48613918e2f309f7405ecb3b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8163 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-17 09:17:29 +00:00
"third_party:khronos_platform",
OpenGL: Don't use glad to load OpenGL entrypoints This makes the OpenGL entry points loaded at Adapter creation from the getProcAddress passed in the DiscoveryOptions and update all GL calls in the backend to go through the new OpenGLFunctions object. A code generator is added that generates the function loader and list of GL procs from Khronos' gl.xml file but we can't get rid of glad yet because it is used to have the PROC typedefs and enum values. BUG=dawn:165 Change-Id: I2a583d79752f55877fa4190846f5be16cf91651a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7983 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-13 10:22:32 +00:00
]
sources += get_target_outputs(":libdawn_native_opengl_loader_gen")
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
sources += [
OpenGL: Implement the backend connection and adapter. The OpenGL backend can't gather discover default adapters because it needs getProc to do anything so we add DiscoverAdapters method to Instance that takes backend-specific options. dawn_native::opengl::CreateDevice is removed in favor of the adapter path so OpenGLBinding is modified to create an instance locally. This is only temporary until all backends support adapters, at which point a lot of *Binding code will be factored. Also contains a small fix for Result<T, E> with movable types. BUG=dawn:29 Change-Id: I4eb3d4a14a871af73e1872132aff72b45e5fe566 Reviewed-on: https://dawn-review.googlesource.com/c/3663 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-07 09:48:03 +00:00
"src/dawn_native/opengl/BackendGL.cpp",
"src/dawn_native/opengl/BackendGL.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/opengl/BufferGL.cpp",
"src/dawn_native/opengl/BufferGL.h",
"src/dawn_native/opengl/CommandBufferGL.cpp",
"src/dawn_native/opengl/CommandBufferGL.h",
"src/dawn_native/opengl/ComputePipelineGL.cpp",
"src/dawn_native/opengl/ComputePipelineGL.h",
"src/dawn_native/opengl/DeviceGL.cpp",
"src/dawn_native/opengl/DeviceGL.h",
"src/dawn_native/opengl/Forward.h",
Introduce a format table in the OpenGL The information about formats in OpenGL will grow to include more information than just (internalFormat, format, type) and will gain more logic to depend on GL version and available extensions over time. BUG=dawn:128 Change-Id: I63a6ac7d48797fb4a9f97a65871306e640cf41d6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9201 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Jiawei Shao <jiawei.shao@intel.com> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-07-23 06:40:54 +00:00
"src/dawn_native/opengl/GLFormat.cpp",
"src/dawn_native/opengl/GLFormat.h",
Remove OpenGLBinding's dependency on glad This move all the OpenGL-specific code for swapchain handling in a new NativeSwapChainImpl in the OpenGL backend so no code outside of dawn_native needs OpenGL. BUG=dawn:165 Change-Id: I3c0c1055e3215a59fdc8e9550baf30762a7014b5 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8161 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-06-17 09:01:09 +00:00
"src/dawn_native/opengl/NativeSwapChainImplGL.cpp",
"src/dawn_native/opengl/NativeSwapChainImplGL.h",
OpenGL: Don't use glad to load OpenGL entrypoints This makes the OpenGL entry points loaded at Adapter creation from the getProcAddress passed in the DiscoveryOptions and update all GL calls in the backend to go through the new OpenGLFunctions object. A code generator is added that generates the function loader and list of GL procs from Khronos' gl.xml file but we can't get rid of glad yet because it is used to have the PROC typedefs and enum values. BUG=dawn:165 Change-Id: I2a583d79752f55877fa4190846f5be16cf91651a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7983 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-13 10:22:32 +00:00
"src/dawn_native/opengl/OpenGLFunctions.cpp",
"src/dawn_native/opengl/OpenGLFunctions.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/opengl/PersistentPipelineStateGL.cpp",
"src/dawn_native/opengl/PersistentPipelineStateGL.h",
"src/dawn_native/opengl/PipelineGL.cpp",
"src/dawn_native/opengl/PipelineGL.h",
"src/dawn_native/opengl/PipelineLayoutGL.cpp",
"src/dawn_native/opengl/PipelineLayoutGL.h",
"src/dawn_native/opengl/QueueGL.cpp",
"src/dawn_native/opengl/QueueGL.h",
"src/dawn_native/opengl/RenderPipelineGL.cpp",
"src/dawn_native/opengl/RenderPipelineGL.h",
"src/dawn_native/opengl/SamplerGL.cpp",
"src/dawn_native/opengl/SamplerGL.h",
"src/dawn_native/opengl/ShaderModuleGL.cpp",
"src/dawn_native/opengl/ShaderModuleGL.h",
"src/dawn_native/opengl/SwapChainGL.cpp",
"src/dawn_native/opengl/SwapChainGL.h",
"src/dawn_native/opengl/TextureGL.cpp",
"src/dawn_native/opengl/TextureGL.h",
Complete the sampler object to match WebGPU WebGPUSampler is much more complete than Dawn's Sampler. This patch implement the missing part. BUG=dawn:47 Change-Id: Ief45cb9710493e9d79ddab60fe3be5a123b76ebd Reviewed-on: https://dawn-review.googlesource.com/c/3540 Commit-Queue: Shaobo Yan <shaobo.yan@intel.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-04 04:56:08 +00:00
"src/dawn_native/opengl/UtilsGL.cpp",
"src/dawn_native/opengl/UtilsGL.h",
Remove glad and replace it with our own GL header This completely removes the dependency on glad by generating the GL headers from gl.xml directly. This requires adding khrplatform.h so all Khronos dependencies are gathered in third_party/khronos. Also removes a stray CMakeLists.txt that was still hanging out. BUG=dawn:165 Change-Id: Ia64bc51bc8b18c6b48613918e2f309f7405ecb3b Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8163 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-06-17 09:17:29 +00:00
"src/dawn_native/opengl/opengl_platform.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
}
if (dawn_enable_vulkan) {
Fix compilation of the OpenGL backend on Mac OpenGLBackend.cpp would end up including KHR/khrplatform.h when the libdawn_native target that contains it doesn't have a dependency on the khr_platform target. Fix this by making libdawn_native_sources expose some of its dependencies as public_deps. BUG= Change-Id: I45c05a064e4b73ab7ac6f5f6258e7983e5fc085d Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/9205 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Kai Ninomiya <kainino@chromium.org>
2019-07-22 23:32:29 +00:00
public_deps += [ "third_party:vulkan_headers" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
sources += [
Vulkan: Implement the backend connection and adapter. This also changes VulkanInfo to gather info on backends / adapters instead of the device, because all the info gathering can happen before the device is created. BUG=dawn:29 Change-Id: I9dc4412f494428f1ae589544d3adf76fe8b9a3a3 Reviewed-on: https://dawn-review.googlesource.com/c/3941 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-02-04 09:31:09 +00:00
"src/dawn_native/vulkan/AdapterVk.cpp",
"src/dawn_native/vulkan/AdapterVk.h",
"src/dawn_native/vulkan/BackendVk.cpp",
"src/dawn_native/vulkan/BackendVk.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/BindGroupLayoutVk.cpp",
"src/dawn_native/vulkan/BindGroupLayoutVk.h",
"src/dawn_native/vulkan/BindGroupVk.cpp",
"src/dawn_native/vulkan/BindGroupVk.h",
"src/dawn_native/vulkan/BufferVk.cpp",
"src/dawn_native/vulkan/BufferVk.h",
"src/dawn_native/vulkan/CommandBufferVk.cpp",
"src/dawn_native/vulkan/CommandBufferVk.h",
Normalize generated file paths to match main tree. Previously dawn_native files were in src/dawn_native/ while generated files were in dawn_native/. This makes some things complicated when integrating in other source trees so normalize all generated files to be in paths that match the main tree. BUG=dawn:225 Change-Id: I5b3e04d37a16251143578dfb7a31445b229fe4ac Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11300 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:33:12 +00:00
"src/dawn_native/vulkan/CommandRecordingContext.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/ComputePipelineVk.cpp",
"src/dawn_native/vulkan/ComputePipelineVk.h",
Vulkan: Reuse descriptor pools This changes puts descriptor pools in the BindGroupLayout so that they can be reused between descriptors with the same layout. This makes the DrawCallPerf.Run/Vulkan_NoReuseBindGroups benchmark go from 1400ns to 800ns per run. BUG=dawn::256 Change-Id: Ia9baf7f998d9ff4d552e255c80069b67c6a9ac40 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12920 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org>
2019-11-05 15:44:05 +00:00
"src/dawn_native/vulkan/DescriptorSetService.cpp",
"src/dawn_native/vulkan/DescriptorSetService.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/DeviceVk.cpp",
"src/dawn_native/vulkan/DeviceVk.h",
Add wrapping for using external vulkan images as textures This change adds platform-dependent services that handle creating semaphores and importing image memory. Then, we use them to wrap a texture from an outside source, and release a signal semaphore back when we're done with it. This will be used to allow chrome to render dawn on Vulkan platforms. Bug: chromium:976495 Change-Id: I9f07eaf436e10aa6bd88cffdc74fd23834d62ee0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8340 Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-10 03:17:52 +00:00
"src/dawn_native/vulkan/ExternalHandle.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/FencedDeleter.cpp",
"src/dawn_native/vulkan/FencedDeleter.h",
"src/dawn_native/vulkan/Forward.h",
"src/dawn_native/vulkan/NativeSwapChainImplVk.cpp",
"src/dawn_native/vulkan/NativeSwapChainImplVk.h",
"src/dawn_native/vulkan/PipelineLayoutVk.cpp",
"src/dawn_native/vulkan/PipelineLayoutVk.h",
"src/dawn_native/vulkan/QueueVk.cpp",
"src/dawn_native/vulkan/QueueVk.h",
"src/dawn_native/vulkan/RenderPassCache.cpp",
"src/dawn_native/vulkan/RenderPassCache.h",
"src/dawn_native/vulkan/RenderPipelineVk.cpp",
"src/dawn_native/vulkan/RenderPipelineVk.h",
Vulkan: Use the ResourceMemoryAllocator for all resources This removes the duplication of the memory allocators in preparation for using sub-allocation in the Vulkan backend too. Also renames ResourceMemory to ResourceHeap and MemoryResourceAllocator to ResourceMemoryAllocator, and fixes a number of unused includes. BUG=dawn:27 Change-Id: I1a9e7d41e5efafa5192bda1d89dc06455fa2af40 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12660 Reviewed-by: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-10-24 21:24:27 +00:00
"src/dawn_native/vulkan/ResourceHeapVk.cpp",
"src/dawn_native/vulkan/ResourceHeapVk.h",
"src/dawn_native/vulkan/ResourceMemoryAllocatorVk.cpp",
"src/dawn_native/vulkan/ResourceMemoryAllocatorVk.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/SamplerVk.cpp",
"src/dawn_native/vulkan/SamplerVk.h",
"src/dawn_native/vulkan/ShaderModuleVk.cpp",
"src/dawn_native/vulkan/ShaderModuleVk.h",
Memory manager: buffer uploads (Vulkan) - Part 2 Manages a single persistently mapped GPU heap which is sub-allocated inside of ring-buffer for uploads. To handle larger buffers without additional unused heaps, ring buffers are created on-demand. BUG=dawn:28 TEST=dawn_unittests Change-Id: Ic2a5df3142fc24fa772b9a85b38248eea8c7e003 Reviewed-on: https://dawn-review.googlesource.com/c/4260 Commit-Queue: Bryan Bernhart <bryan.bernhart@intel.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-02-06 18:10:12 +00:00
"src/dawn_native/vulkan/StagingBufferVk.cpp",
"src/dawn_native/vulkan/StagingBufferVk.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/SwapChainVk.cpp",
"src/dawn_native/vulkan/SwapChainVk.h",
"src/dawn_native/vulkan/TextureVk.cpp",
"src/dawn_native/vulkan/TextureVk.h",
Complete the sampler object to match WebGPU WebGPUSampler is much more complete than Dawn's Sampler. This patch implement the missing part. BUG=dawn:47 Change-Id: Ief45cb9710493e9d79ddab60fe3be5a123b76ebd Reviewed-on: https://dawn-review.googlesource.com/c/3540 Commit-Queue: Shaobo Yan <shaobo.yan@intel.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-04 04:56:08 +00:00
"src/dawn_native/vulkan/UtilsVulkan.cpp",
"src/dawn_native/vulkan/UtilsVulkan.h",
Vulkan: Print the VkResult value on device creation failure. This adds a CheckVkSuccess utility function that adds the VkResult value to the context lost error message. Also adds a small fix to dawn_native/Error.h interoperability between MaybeError and ResultOrError<NonPointer> with tests. BUG=chromium:917555 BUG=dawn:79 Change-Id: Icc01122d62d83693fc0ea3f26b272f2372fd3087 Reviewed-on: https://dawn-review.googlesource.com/c/3623 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-04 10:18:40 +00:00
"src/dawn_native/vulkan/VulkanError.cpp",
"src/dawn_native/vulkan/VulkanError.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"src/dawn_native/vulkan/VulkanFunctions.cpp",
"src/dawn_native/vulkan/VulkanFunctions.h",
"src/dawn_native/vulkan/VulkanInfo.cpp",
"src/dawn_native/vulkan/VulkanInfo.h",
Add wrapping for using external vulkan images as textures This change adds platform-dependent services that handle creating semaphores and importing image memory. Then, we use them to wrap a texture from an outside source, and release a signal semaphore back when we're done with it. This will be used to allow chrome to render dawn on Vulkan platforms. Bug: chromium:976495 Change-Id: I9f07eaf436e10aa6bd88cffdc74fd23834d62ee0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8340 Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-10 03:17:52 +00:00
"src/dawn_native/vulkan/external_memory/MemoryService.h",
"src/dawn_native/vulkan/external_semaphore/SemaphoreService.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
Add wrapping for using external vulkan images as textures This change adds platform-dependent services that handle creating semaphores and importing image memory. Then, we use them to wrap a texture from an outside source, and release a signal semaphore back when we're done with it. This will be used to allow chrome to render dawn on Vulkan platforms. Bug: chromium:976495 Change-Id: I9f07eaf436e10aa6bd88cffdc74fd23834d62ee0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8340 Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-10 03:17:52 +00:00
Implement a dma-buf MemoryService This CL implements the MemoryService for importing memory and creating VkImages from a dma-buf handle. Under the hood, it uses the VK_EXT_external_memory_dma_buf and VK_EXT_image_drm_format_modifier extensions to find a memory type that supports dma-buf import. In addition, the extensions are also used to properly specify the stride and tiling of the dma-buf to vkAllocateMemory and vkCreateImage. BUG=chromium:996470 Change-Id: Ie72d73117a4cbafcb40468aab0952b783351d499 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13785 Commit-Queue: Brian Ho <hob@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-11-21 16:02:10 +00:00
if (is_chromeos) {
sources += [
"src/dawn_native/vulkan/external_memory/MemoryServiceDmaBuf.cpp",
"src/dawn_native/vulkan/external_semaphore/SemaphoreServiceOpaqueFD.cpp",
]
} else if (is_linux) {
Add wrapping for using external vulkan images as textures This change adds platform-dependent services that handle creating semaphores and importing image memory. Then, we use them to wrap a texture from an outside source, and release a signal semaphore back when we're done with it. This will be used to allow chrome to render dawn on Vulkan platforms. Bug: chromium:976495 Change-Id: I9f07eaf436e10aa6bd88cffdc74fd23834d62ee0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8340 Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-10 03:17:52 +00:00
sources += [
"src/dawn_native/vulkan/external_memory/MemoryServiceOpaqueFD.cpp",
"src/dawn_native/vulkan/external_semaphore/SemaphoreServiceOpaqueFD.cpp",
]
[fuchsia] Implement external semaphore and memory support. This CL adds Fuchsia-specific implementations to the following classes: dawn_native::vulkan::external_memory::Service dawn_native::vulkan::external_semaphore::Service The implementation is based on two Fuchsia Vulkan extensions that are provides by the vulkan_fuchsia_extras.h header (i.e. are not upstreamed to Khronos yet, but used/provided by the Fuchsia platform): VK_FUCHSIA_external_memory VK_FUCHSIA_external_semaphore Their details are similar to VK_KHR_external_XXXX_fd, but uses Zircon handles instead of file decriptors. BUG=dawn:221 Change-Id: I48238bcf3193433970cbe200a84b86a67103a2f2 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/10963 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: David Turner <digit@google.com>
2019-09-10 10:07:28 +00:00
} else if (is_fuchsia) {
sources += [
"src/dawn_native/vulkan/external_memory/MemoryServiceZirconHandle.cpp",
"src/dawn_native/vulkan/external_semaphore/SemaphoreServiceZirconHandle.cpp",
]
Add wrapping for using external vulkan images as textures This change adds platform-dependent services that handle creating semaphores and importing image memory. Then, we use them to wrap a texture from an outside source, and release a signal semaphore back when we're done with it. This will be used to allow chrome to render dawn on Vulkan platforms. Bug: chromium:976495 Change-Id: I9f07eaf436e10aa6bd88cffdc74fd23834d62ee0 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8340 Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-08-10 03:17:52 +00:00
} else {
sources += [
"src/dawn_native/vulkan/external_memory/MemoryServiceNull.cpp",
"src/dawn_native/vulkan/external_semaphore/SemaphoreServiceNull.cpp",
]
}
Enable Vulkan for Chromium Fuchsia build. Enable the Vulkan backend when building Dawn with the Chromium build system for Fuchsia. To make this work properly the following is required: - Modify VulkanInfo.cpp and BackendVk.cpp to correctly probe the Fuchsia swapchain layer and its layer extension, as well as enabling them when creating a new VkInstance. - Modify VulkanFunctions.cpp to load the Fuchsia swapchain related extension for this platform only. - Provide a small mock GLFW library for Fuchsia under src/utils/Glfw3Fuchsia.cpp, since the upstream project does not support this platform at all. Its purpose is only to allow the creation of the right VulkanBinding instance, which depends on the creation of a display surface for latter swapchain creation. - Add //third_party/fuchsia-sdk:vulkan_base and //third_party/fuchsia-sdk:vulkan_validation as data_deps of the libdawn_native_sources target in order to ensure that the Fuchsia package created by the build system will include the correct Vulkan libraries (loader and validation layers). This builds correctly, and both dawn_unittests and dawn_end2end_tests will run on a real Fuchsia device or inside the Fuchsia emulator, using either GPU virtualization or a software-based renderer. Note: dawn_unittests will also run inside QEMU, but not dawn_end2end_tests, since the latter requires proper GPU emulation which is not available in this environment. NOTE: All end2end tests pass using a device with an "Intel HD Graphics 615 (Kaby Lake GT2)" adapter. However: - For some reason, a single test takes up to 129 seconds to pass (BufferSetSubDataTests.ManySetSubData/Vulkan). - The test process crashes inside VkDestroyInstance(), apparently inside the Fuchsia-specific imagepipe layer (which implements swapchain support). This is likely a bug in the layer itself, and not Dawn. Also, may end2end tests will crash when run inside the Fuchsia emulator (which uses GPU virtualization to talk to the host GPU). The crashes happen inside libvulkan-goldfish.so, the emulator-specific Vulkan ICD on this sytem. Not a Dawn bug either. Bug=dawn:221 Change-Id: Id3598b673e8c6393f24db728b8da49fdde3cac76 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8963 Commit-Queue: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org>
2019-09-09 10:52:08 +00:00
if (build_with_chromium && is_fuchsia) {
# Necessary to ensure that the Vulkan libraries will be in the
# final Fuchsia package.
data_deps = [
# NOTE: The line below is a work around for http://crbug.com/1001081
"//third_party/fuchsia-sdk/sdk:trace_engine",
"//third_party/fuchsia-sdk:vulkan_base",
"//third_party/fuchsia-sdk:vulkan_validation",
]
}
Add Vulkan validation layers on Windows Deploy self-built Vulkan validation layers instead of system installed one. And it will reuse third_party/angle's Vulkan validation layers if building with chromium. Bug: dawn:150 Change-Id: I94e26f7a152fb2a1c39bcb102d60024f4d65eee6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11120 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-11-07 12:13:27 +00:00
if (dawn_enable_vulkan_validation_layers) {
Add in flag for using spvc instead of direct spriv-cross access Currently does nothing interesting, future CLs will flesh out the functionality. BUG=dawn:281 Change-Id: I89750a45ff5a42a13e1494cafd433bb7ef719b10 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13841 Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Ryan Harrison <rharrison@chromium.org>
2019-11-20 18:10:11 +00:00
defines += [
Add Vulkan validation layers on Windows Deploy self-built Vulkan validation layers instead of system installed one. And it will reuse third_party/angle's Vulkan validation layers if building with chromium. Bug: dawn:150 Change-Id: I94e26f7a152fb2a1c39bcb102d60024f4d65eee6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11120 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-11-07 12:13:27 +00:00
"DAWN_ENABLE_VULKAN_VALIDATION_LAYERS",
"DAWN_VK_DATA_DIR=\"$vulkan_data_subdir\"",
]
}
Allow using swiftshader with the Vulkan backend This adds swiftshader as a dependency of Dawn, and when it is present dawn_use_swiftshader=true will force usage of it. (due to a Vulkan loader limitation we can't have both regular drivers and swiftshader in the same VkInstance). BUG=dawn:283 Change-Id: Ib94f4dcca652eb380e994f007cdcfb145b1a5102 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/13440 Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-11-26 18:21:51 +00:00
if (use_swiftshader) {
data_deps += [ "${dawn_swiftshader_dir}/src/Vulkan:icd_file" ]
defines +=
[ "DAWN_SWIFTSHADER_VK_ICD_JSON=\"${swiftshader_icd_file_name}\"" ]
}
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
}
}
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
# The static and shared libraries for libdawn_native. Most of the files are
# already compiled in libdawn_native_sources, but we still need to compile
# files defining exported symbols.
BUILD.gn: Change the static/shared library template to component This changes the dawn_static_and_shared_library template to be a dawn_component template that mimics the behavior of Chromium's components. This helps avoid issues where on non-component builds on Windows the CRT would get linked statically in both the Dawn shared libraries and the test executables, causing alloc/deallocs across library boundaries to crash. BUG=dawn:29 Change-Id: I69287a523cc0bf5f2e921982ea9c26dcfed82f11 Reviewed-on: https://dawn-review.googlesource.com/c/4040 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-25 03:20:20 +00:00
dawn_component("libdawn_native") {
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
DEFINE_PREFIX = "DAWN_NATIVE"
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
#Make headers publically visible
public_deps = [
":libdawn_native_headers",
]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
deps = [
Add wire_cmd.py and dawn_wire.json to autogenerate all wire commands. Unify code generation for Client->Server and Server->Client commands. Methods in dawn.json are converted into command records and additional commands are specified in dawn_wire.json. This can then be used to completely generate the command handlers and command struct definitions. Bug: dawn:88 Change-Id: Ic796796ede0aafe02e14f1f96790324dad92f4c0 Reviewed-on: https://dawn-review.googlesource.com/c/3800 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-15 20:49:53 +00:00
":libdawn_native_sources",
Split off common and libdawn / dawn_headers from BUILD.gn This adds an option to dawn_generator to generate files in a different directory so the generated stay at the same place. Otherwise compilation errors occur because of stale versions of the headers on the CQ builders. BUG=dawn:61 Change-Id: I71ceb3172b5a4e35911973a03be29d90fa684416 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5304 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-07 01:46:39 +00:00
"${dawn_root}/src/common",
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
]
sources = [
"src/dawn_native/DawnNative.cpp",
]
configs = [ ":libdawn_native_internal" ]
Move ldflags (Metal dependency) to libdawn_native. Bug: chromium:1003381 Change-Id: I1cb0f0404dde9936f4fb8f64588535a84e50c957 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/12600 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Nico Weber <thakis@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-10-24 09:44:13 +00:00
public_configs = [ ":libdawn_native_weak_framework" ]
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
if (dawn_enable_d3d12) {
sources += [ "src/dawn_native/d3d12/D3D12Backend.cpp" ]
}
if (dawn_enable_metal) {
sources += [ "src/dawn_native/metal/MetalBackend.mm" ]
}
if (dawn_enable_null) {
sources += [ "src/dawn_native/null/NullBackend.cpp" ]
}
if (dawn_enable_opengl) {
sources += [ "src/dawn_native/opengl/OpenGLBackend.cpp" ]
}
if (dawn_enable_vulkan) {
sources += [ "src/dawn_native/vulkan/VulkanBackend.cpp" ]
Add Vulkan validation layers on Windows Deploy self-built Vulkan validation layers instead of system installed one. And it will reuse third_party/angle's Vulkan validation layers if building with chromium. Bug: dawn:150 Change-Id: I94e26f7a152fb2a1c39bcb102d60024f4d65eee6 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11120 Commit-Queue: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-11-07 12:13:27 +00:00
if (dawn_enable_vulkan_validation_layers) {
data_deps = [
"${dawn_vulkan_validation_layers_dir}:vulkan_validation_layers",
]
if (!is_android) {
data_deps +=
[ "${dawn_vulkan_validation_layers_dir}:vulkan_gen_json_files" ]
}
}
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
}
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
}
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
###############################################################################
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
# libdawn_wire
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
###############################################################################
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
Generators: main.py is now dawn_json_generator.py This merges all the files for main.py together again except generator_lib.py because there doesn't seeem to be a good way to separate the pure dawn.json generators and the dawn wire generator. Also updates the GN templates to make it easier to define new generators based on generator_lib, and move the Jinja2 template "stdlib" to generator_lib.py BUG=dawn:165 Change-Id: I1b5b2ef0a59cb142e214f3af9a58048a88ae949a Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/7880 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-06-11 18:03:05 +00:00
dawn_json_generator("libdawn_wire_gen") {
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
target = "dawn_wire"
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
outputs = [
Normalize generated file paths to match main tree. Previously dawn_native files were in src/dawn_native/ while generated files were in dawn_native/. This makes some things complicated when integrating in other source trees so normalize all generated files to be in paths that match the main tree. BUG=dawn:225 Change-Id: I5b3e04d37a16251143578dfb7a31445b229fe4ac Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11300 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-18 04:33:12 +00:00
"src/dawn_wire/WireCmd_autogen.h",
"src/dawn_wire/WireCmd_autogen.cpp",
"src/dawn_wire/client/ApiObjects_autogen.h",
"src/dawn_wire/client/ApiProcs_autogen.cpp",
"src/dawn_wire/client/ApiProcs_autogen.h",
"src/dawn_wire/client/ClientBase_autogen.h",
"src/dawn_wire/client/ClientHandlers_autogen.cpp",
"src/dawn_wire/client/ClientPrototypes_autogen.inc",
"src/dawn_wire/server/ServerBase_autogen.h",
"src/dawn_wire/server/ServerDoers_autogen.cpp",
"src/dawn_wire/server/ServerHandlers_autogen.cpp",
"src/dawn_wire/server/ServerPrototypes_autogen.inc",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
}
BUILD.gn: Change the static/shared library template to component This changes the dawn_static_and_shared_library template to be a dawn_component template that mimics the behavior of Chromium's components. This helps avoid issues where on non-component builds on Windows the CRT would get linked statically in both the Dawn shared libraries and the test executables, causing alloc/deallocs across library boundaries to crash. BUG=dawn:29 Change-Id: I69287a523cc0bf5f2e921982ea9c26dcfed82f11 Reviewed-on: https://dawn-review.googlesource.com/c/4040 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-25 03:20:20 +00:00
dawn_component("libdawn_wire") {
Add static library versions of libdawn* Chromium will want to have both static and shared library versions of Dawn to use in non-component and component builds respectively. The *_export.h files are modified to noop when *_SHARED_LIBRARY is not defined so that the static library doesn't export symbols that aren't imported in dependents (this would break compilation on Windows). A dawn_library_combo is introduced in BUILD.gn that factors out all the logic needed to produce shared libraries and handle the _EXPORT macros. Also contains a fix to dawncpp to export only the methods that aren't defined in the header (otherwise they get defined multiple times) BUG=dawn:85 Change-Id: Ib747deb9308e1165dd66002487147ba279d3eac0 Reviewed-on: https://dawn-review.googlesource.com/c/3761 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-01-09 09:05:18 +00:00
DEFINE_PREFIX = "DAWN_WIRE"
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
deps = [
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
":libdawn_wire_gen",
Split off common and libdawn / dawn_headers from BUILD.gn This adds an option to dawn_generator to generate files in a different directory so the generated stay at the same place. Otherwise compilation errors occur because of stale versions of the headers on the CQ builders. BUG=dawn:61 Change-Id: I71ceb3172b5a4e35911973a03be29d90fa684416 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5304 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-07 01:46:39 +00:00
"${dawn_root}/src/common",
Split off libdawn_wire_headers from BUILD.gn These need to be separated from the main BUILD.gn as well. They cannot be easily guarded behind build flags in Chromium because the WebGPUImplementation will extend dawn_wire::CommandSerializer. Bug: dawn:61 Change-Id: Ic7d6bb13cc535ecddb99c832407ba1f37019ed93 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5401 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-03-08 00:51:27 +00:00
"${dawn_root}/src/dawn_wire:libdawn_wire_headers",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
Make Dawn "gn check" by default (except SPIRV-Tools) This required adding some missing dependencies, splitting public headers of libdawn_[native|wire] so they aren't hidden in the libdawn_[native|wire]_sources targets, and making unittests depend on sources directly instead of static libraries (which is almost equivalent). As a byproduct, Empty.cpp is no longer needed and is removed.
2018-08-12 19:07:46 +00:00
Split off common and libdawn / dawn_headers from BUILD.gn This adds an option to dawn_generator to generate files in a different directory so the generated stay at the same place. Otherwise compilation errors occur because of stale versions of the headers on the CQ builders. BUG=dawn:61 Change-Id: I71ceb3172b5a4e35911973a03be29d90fa684416 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5304 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-03-07 01:46:39 +00:00
configs = [ "${dawn_root}/src/common:dawn_internal" ]
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
sources = get_target_outputs(":libdawn_wire_gen")
Add wire_cmd.py and dawn_wire.json to autogenerate all wire commands. Unify code generation for Client->Server and Server->Client commands. Methods in dawn.json are converted into command records and additional commands are specified in dawn_wire.json. This can then be used to completely generate the command handlers and command struct definitions. Bug: dawn:88 Change-Id: Ic796796ede0aafe02e14f1f96790324dad92f4c0 Reviewed-on: https://dawn-review.googlesource.com/c/3800 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-15 20:49:53 +00:00
sources += [
Create wire Client and Server classes with private impl This creates proper Client and Server interfaces which will be necessary for adding additional features to the Wire for chrome integration Bug: dawn:103 Change-Id: I181e95079b0bac85c2c6152ad8066a94b80c8d28 Reviewed-on: https://dawn-review.googlesource.com/c/4002 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-02-11 21:50:16 +00:00
"src/dawn_wire/WireClient.cpp",
Add wire_cmd.py and dawn_wire.json to autogenerate all wire commands. Unify code generation for Client->Server and Server->Client commands. Methods in dawn.json are converted into command records and additional commands are specified in dawn_wire.json. This can then be used to completely generate the command handlers and command struct definitions. Bug: dawn:88 Change-Id: Ic796796ede0aafe02e14f1f96790324dad92f4c0 Reviewed-on: https://dawn-review.googlesource.com/c/3800 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-15 20:49:53 +00:00
"src/dawn_wire/WireDeserializeAllocator.cpp",
"src/dawn_wire/WireDeserializeAllocator.h",
Create wire Client and Server classes with private impl This creates proper Client and Server interfaces which will be necessary for adding additional features to the Wire for chrome integration Bug: dawn:103 Change-Id: I181e95079b0bac85c2c6152ad8066a94b80c8d28 Reviewed-on: https://dawn-review.googlesource.com/c/4002 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-02-11 21:50:16 +00:00
"src/dawn_wire/WireServer.cpp",
Separate WireClient.cpp into multiple files. This patch copies methods and classes from WireClient.cpp and distributes them over multiple files. Headers and forward declarations are added as necessary, but no logical changes are made. Bug: dawn:88 Change-Id: I9d0fcaeb67e789c3ad0597eaa3839adefc3ac5f9 Reviewed-on: https://dawn-review.googlesource.com/c/3980 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-01-16 02:18:06 +00:00
"src/dawn_wire/client/ApiObjects.h",
"src/dawn_wire/client/ApiProcs.cpp",
"src/dawn_wire/client/Buffer.cpp",
"src/dawn_wire/client/Buffer.h",
"src/dawn_wire/client/Client.cpp",
"src/dawn_wire/client/Client.h",
Factor wire client handlers into proper command handlers and doers Bug: dawn:88 Change-Id: I3ab28efad7edc7d06f11aa5abae07a1bb3d7e59e Reviewed-on: https://dawn-review.googlesource.com/c/4003 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-30 03:00:17 +00:00
"src/dawn_wire/client/ClientDoers.cpp",
Add MemoryTransfer interfaces to the wire This patch adds MemoryTransfer client/server interfaces and uses it to implement data transfers for buffer mapping. This patch also provides a default "inline" implementation of the MemoryTransfer which is used if the embedder does not provide one on initialization. Because implementations of MemoryTransfer perform their own serialization, a skip_serialize option is added to WireCmd records. Bug: dawn:156 Change-Id: I2fa035517628a3ad465b0bc18a6ffc477e2bd67f Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8642 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-07-19 16:01:48 +00:00
"src/dawn_wire/client/ClientInlineMemoryTransferService.cpp",
Make the wire Client own ObjectAllocators and CommandSerializer This moves ownership of ObjectAllocators and CommandSerializers from the Device to the Client. There may be also be multiple Devices, so New() now takes the Device the object belongs to. Device allocation specializes New() to take the owning Client so that we can get a pointer to the Client from any Dawn API object. Bug: dawn:88 Change-Id: Ie4274d46313884c44a857159e95d236dc1141c0c Reviewed-on: https://dawn-review.googlesource.com/c/4001 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org>
2019-01-30 02:31:37 +00:00
"src/dawn_wire/client/Device.cpp",
"src/dawn_wire/client/Device.h",
Separate WireClient.cpp into multiple files. This patch copies methods and classes from WireClient.cpp and distributes them over multiple files. Headers and forward declarations are added as necessary, but no logical changes are made. Bug: dawn:88 Change-Id: I9d0fcaeb67e789c3ad0597eaa3839adefc3ac5f9 Reviewed-on: https://dawn-review.googlesource.com/c/3980 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-01-16 02:18:06 +00:00
"src/dawn_wire/client/Fence.cpp",
"src/dawn_wire/client/Fence.h",
"src/dawn_wire/client/ObjectAllocator.h",
Separate WireServer.cpp into multiple files. This patch copies methods and classes from WireServer.cpp and distributes them over multiple files. Headers and forward declarations are added as necessary, but no functional changes are made. Bug: dawn:88 Change-Id: I471b8c27804916257eff266a51d087ba1ddbfeb6 Reviewed-on: https://dawn-review.googlesource.com/c/4000 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-01-30 02:20:58 +00:00
"src/dawn_wire/server/ObjectStorage.h",
"src/dawn_wire/server/Server.cpp",
"src/dawn_wire/server/Server.h",
"src/dawn_wire/server/ServerBuffer.cpp",
"src/dawn_wire/server/ServerDevice.cpp",
"src/dawn_wire/server/ServerFence.cpp",
Add MemoryTransfer interfaces to the wire This patch adds MemoryTransfer client/server interfaces and uses it to implement data transfers for buffer mapping. This patch also provides a default "inline" implementation of the MemoryTransfer which is used if the embedder does not provide one on initialization. Because implementations of MemoryTransfer perform their own serialization, a skip_serialize option is added to WireCmd records. Bug: dawn:156 Change-Id: I2fa035517628a3ad465b0bc18a6ffc477e2bd67f Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8642 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-07-19 16:01:48 +00:00
"src/dawn_wire/server/ServerInlineMemoryTransferService.cpp",
Separate WireServer.cpp into multiple files. This patch copies methods and classes from WireServer.cpp and distributes them over multiple files. Headers and forward declarations are added as necessary, but no functional changes are made. Bug: dawn:88 Change-Id: I471b8c27804916257eff266a51d087ba1ddbfeb6 Reviewed-on: https://dawn-review.googlesource.com/c/4000 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-01-30 02:20:58 +00:00
"src/dawn_wire/server/ServerQueue.cpp",
Add wire_cmd.py and dawn_wire.json to autogenerate all wire commands. Unify code generation for Client->Server and Server->Client commands. Methods in dawn.json are converted into command records and additional commands are specified in dawn_wire.json. This can then be used to completely generate the command handlers and command struct definitions. Bug: dawn:88 Change-Id: Ic796796ede0aafe02e14f1f96790324dad92f4c0 Reviewed-on: https://dawn-review.googlesource.com/c/3800 Commit-Queue: Austin Eng <enga@chromium.org> Reviewed-by: Corentin Wallez <cwallez@chromium.org>
2019-01-15 20:49:53 +00:00
]
BUILD.gn: Remove use of exec_script Chromium's BUILD files try to avoid uses of exec_script when possible because they slow down every GN invocation. In preparation for building Dawn inside Chromium, the calls to exec_script for the code generator are removed. In GN, the generator now outputs a "JSON tarball", a dictionnary mapping filenames to content. This allows us to use the "depfile" feature of GN to avoid the exec_script call to gather the script's inputs. Outputs of the generator are now listed in the BUILD.gn files. To keep it in sync with the generator, GN outputs a file containing "expected outputs" that is checked by the code generator. Finally the dawn_generator GN template doesn't create a target anymore, but users are expected to gather outputs using get_target_outputs.
2018-08-16 13:32:35 +00:00
Don't use shared libraries in the wire fuzzer. Otherwise UBSan complains that C++ types are different between the shared libraries because libc++ is linked statically. BUG=chromium:904736 Change-Id: I51ef40d1f7910fd693a4585c74ff404812472d2e Reviewed-on: https://dawn-review.googlesource.com/c/2380 Reviewed-by: Dan Sinclair <dsinclair@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2018-11-14 21:04:26 +00:00
# Make headers publically visible
public_deps = [
Split off libdawn_wire_headers from BUILD.gn These need to be separated from the main BUILD.gn as well. They cannot be easily guarded behind build flags in Chromium because the WebGPUImplementation will extend dawn_wire::CommandSerializer. Bug: dawn:61 Change-Id: Ic7d6bb13cc535ecddb99c832407ba1f37019ed93 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/5401 Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Austin Eng <enga@chromium.org>
2019-03-08 00:51:27 +00:00
"${dawn_root}/src/dawn_wire:libdawn_wire_headers",
Don't use shared libraries in the wire fuzzer. Otherwise UBSan complains that C++ types are different between the shared libraries because libc++ is linked statically. BUG=chromium:904736 Change-Id: I51ef40d1f7910fd693a4585c74ff404812472d2e Reviewed-on: https://dawn-review.googlesource.com/c/2380 Reviewed-by: Dan Sinclair <dsinclair@google.com> Reviewed-by: Kai Ninomiya <kainino@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2018-11-14 21:04:26 +00:00
]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
}
Enable Vulkan for Chromium Fuchsia build. Enable the Vulkan backend when building Dawn with the Chromium build system for Fuchsia. To make this work properly the following is required: - Modify VulkanInfo.cpp and BackendVk.cpp to correctly probe the Fuchsia swapchain layer and its layer extension, as well as enabling them when creating a new VkInstance. - Modify VulkanFunctions.cpp to load the Fuchsia swapchain related extension for this platform only. - Provide a small mock GLFW library for Fuchsia under src/utils/Glfw3Fuchsia.cpp, since the upstream project does not support this platform at all. Its purpose is only to allow the creation of the right VulkanBinding instance, which depends on the creation of a display surface for latter swapchain creation. - Add //third_party/fuchsia-sdk:vulkan_base and //third_party/fuchsia-sdk:vulkan_validation as data_deps of the libdawn_native_sources target in order to ensure that the Fuchsia package created by the build system will include the correct Vulkan libraries (loader and validation layers). This builds correctly, and both dawn_unittests and dawn_end2end_tests will run on a real Fuchsia device or inside the Fuchsia emulator, using either GPU virtualization or a software-based renderer. Note: dawn_unittests will also run inside QEMU, but not dawn_end2end_tests, since the latter requires proper GPU emulation which is not available in this environment. NOTE: All end2end tests pass using a device with an "Intel HD Graphics 615 (Kaby Lake GT2)" adapter. However: - For some reason, a single test takes up to 129 seconds to pass (BufferSetSubDataTests.ManySetSubData/Vulkan). - The test process crashes inside VkDestroyInstance(), apparently inside the Fuchsia-specific imagepipe layer (which implements swapchain support). This is likely a bug in the layer itself, and not Dawn. Also, may end2end tests will crash when run inside the Fuchsia emulator (which uses GPU virtualization to talk to the host GPU). The crashes happen inside libvulkan-goldfish.so, the emulator-specific Vulkan ICD on this sytem. Not a Dawn bug either. Bug=dawn:221 Change-Id: Id3598b673e8c6393f24db728b8da49fdde3cac76 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8963 Commit-Queue: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org>
2019-09-09 10:52:08 +00:00
###############################################################################
# GLFW wrapping target
###############################################################################
BUILD.gn: Only expose the GLFW target on platforms that support it Due to the way GN target discovery works, glfw would get discovered in Fuchsia / Android / ChromeOS builds when it isn't supported causing compilation failures. This changes third_party/BUILD.gn so that glfw targets are only created on supported platforms. It also changes dawn_glfw in BUILD.gn to be more robust to building on all platforms. Bug=dawn:221 BUG=chromium:1002895 Change-Id: I8f40b06f680094406d24e9a6dea44b128e59b854 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11160 Reviewed-by: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-11 16:53:46 +00:00
# GLFW does not support ChromeOS, Android or Fuchsia, so provide a small mock
# library that can be linked into the Dawn tests on these platforms. Otherwise,
# use the real library from third_party/.
BUILD.gn: Correctly skip GLFW on ChromeOS ChromeOS has is_linux = true so the code to skip compiling GLFW on ChromeOS didn't work correctly. BUG=dawn:221 BUG=chromium:1002895 Change-Id: Ifbf8527407ad20b4368531da1d7653ce620d37be Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11200 Reviewed-by: Mitsuru Oshima <oshima@google.com> Reviewed-by: Austin Eng <enga@chromium.org> Reviewed-by: Ahmed Fakhry <afakhry@google.com> Commit-Queue: Austin Eng <enga@chromium.org>
2019-09-12 16:33:31 +00:00
if (is_win || (is_linux && !is_chromeos) || is_mac) {
BUILD.gn: Only expose the GLFW target on platforms that support it Due to the way GN target discovery works, glfw would get discovered in Fuchsia / Android / ChromeOS builds when it isn't supported causing compilation failures. This changes third_party/BUILD.gn so that glfw targets are only created on supported platforms. It also changes dawn_glfw in BUILD.gn to be more robust to building on all platforms. Bug=dawn:221 BUG=chromium:1002895 Change-Id: I8f40b06f680094406d24e9a6dea44b128e59b854 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11160 Reviewed-by: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-11 16:53:46 +00:00
group("dawn_glfw") {
public_deps = [
"third_party:glfw",
]
}
} else if (is_fuchsia) {
# The mock implementation of GLFW on Fuchsia
Enable Vulkan for Chromium Fuchsia build. Enable the Vulkan backend when building Dawn with the Chromium build system for Fuchsia. To make this work properly the following is required: - Modify VulkanInfo.cpp and BackendVk.cpp to correctly probe the Fuchsia swapchain layer and its layer extension, as well as enabling them when creating a new VkInstance. - Modify VulkanFunctions.cpp to load the Fuchsia swapchain related extension for this platform only. - Provide a small mock GLFW library for Fuchsia under src/utils/Glfw3Fuchsia.cpp, since the upstream project does not support this platform at all. Its purpose is only to allow the creation of the right VulkanBinding instance, which depends on the creation of a display surface for latter swapchain creation. - Add //third_party/fuchsia-sdk:vulkan_base and //third_party/fuchsia-sdk:vulkan_validation as data_deps of the libdawn_native_sources target in order to ensure that the Fuchsia package created by the build system will include the correct Vulkan libraries (loader and validation layers). This builds correctly, and both dawn_unittests and dawn_end2end_tests will run on a real Fuchsia device or inside the Fuchsia emulator, using either GPU virtualization or a software-based renderer. Note: dawn_unittests will also run inside QEMU, but not dawn_end2end_tests, since the latter requires proper GPU emulation which is not available in this environment. NOTE: All end2end tests pass using a device with an "Intel HD Graphics 615 (Kaby Lake GT2)" adapter. However: - For some reason, a single test takes up to 129 seconds to pass (BufferSetSubDataTests.ManySetSubData/Vulkan). - The test process crashes inside VkDestroyInstance(), apparently inside the Fuchsia-specific imagepipe layer (which implements swapchain support). This is likely a bug in the layer itself, and not Dawn. Also, may end2end tests will crash when run inside the Fuchsia emulator (which uses GPU virtualization to talk to the host GPU). The crashes happen inside libvulkan-goldfish.so, the emulator-specific Vulkan ICD on this sytem. Not a Dawn bug either. Bug=dawn:221 Change-Id: Id3598b673e8c6393f24db728b8da49fdde3cac76 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8963 Commit-Queue: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org>
2019-09-09 10:52:08 +00:00
config("dawn_glfw_public_config") {
# Allow inclusion of <GLFW/glfw3.h>
[fuchsia]: Fix Fuchsia build. A previous CL broke the build because a GLFW-related config is no longer exposed. This fixes the issue. Bug=dawn:221 Change-Id: I83d43b55d58d18e04ea20f732c76830a798f2487 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11181 Reviewed-by: Corentin Wallez <cwallez@chromium.org> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: David Turner <digit@google.com>
2019-09-12 12:50:31 +00:00
include_dirs = [ "${dawn_glfw_dir}/include" ]
Enable Vulkan for Chromium Fuchsia build. Enable the Vulkan backend when building Dawn with the Chromium build system for Fuchsia. To make this work properly the following is required: - Modify VulkanInfo.cpp and BackendVk.cpp to correctly probe the Fuchsia swapchain layer and its layer extension, as well as enabling them when creating a new VkInstance. - Modify VulkanFunctions.cpp to load the Fuchsia swapchain related extension for this platform only. - Provide a small mock GLFW library for Fuchsia under src/utils/Glfw3Fuchsia.cpp, since the upstream project does not support this platform at all. Its purpose is only to allow the creation of the right VulkanBinding instance, which depends on the creation of a display surface for latter swapchain creation. - Add //third_party/fuchsia-sdk:vulkan_base and //third_party/fuchsia-sdk:vulkan_validation as data_deps of the libdawn_native_sources target in order to ensure that the Fuchsia package created by the build system will include the correct Vulkan libraries (loader and validation layers). This builds correctly, and both dawn_unittests and dawn_end2end_tests will run on a real Fuchsia device or inside the Fuchsia emulator, using either GPU virtualization or a software-based renderer. Note: dawn_unittests will also run inside QEMU, but not dawn_end2end_tests, since the latter requires proper GPU emulation which is not available in this environment. NOTE: All end2end tests pass using a device with an "Intel HD Graphics 615 (Kaby Lake GT2)" adapter. However: - For some reason, a single test takes up to 129 seconds to pass (BufferSetSubDataTests.ManySetSubData/Vulkan). - The test process crashes inside VkDestroyInstance(), apparently inside the Fuchsia-specific imagepipe layer (which implements swapchain support). This is likely a bug in the layer itself, and not Dawn. Also, may end2end tests will crash when run inside the Fuchsia emulator (which uses GPU virtualization to talk to the host GPU). The crashes happen inside libvulkan-goldfish.so, the emulator-specific Vulkan ICD on this sytem. Not a Dawn bug either. Bug=dawn:221 Change-Id: Id3598b673e8c6393f24db728b8da49fdde3cac76 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/8963 Commit-Queue: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org>
2019-09-09 10:52:08 +00:00
# The GLFW/glfw3.h header includes <GL/gl.h> by default, but the latter
# does not exist on Fuchsia. Defining GLFW_INCLUDE_NONE helps work around
# the issue, but it needs to be defined for any file that includes the
# header.
defines = [
"GLFW_INCLUDE_NONE",
"GLFW_INCLUDE_VULKAN",
]
}
static_library("dawn_glfw") {
sources = [
# NOTE: The header below is required to pass "gn check".
"${dawn_glfw_dir}/include/GLFW/glfw3.h",
"src/utils/Glfw3Fuchsia.cpp",
]
public_configs = [ ":dawn_glfw_public_config" ]
deps = [
"${dawn_root}/src/common",
]
}
} else {
BUILD.gn: Only expose the GLFW target on platforms that support it Due to the way GN target discovery works, glfw would get discovered in Fuchsia / Android / ChromeOS builds when it isn't supported causing compilation failures. This changes third_party/BUILD.gn so that glfw targets are only created on supported platforms. It also changes dawn_glfw in BUILD.gn to be more robust to building on all platforms. Bug=dawn:221 BUG=chromium:1002895 Change-Id: I8f40b06f680094406d24e9a6dea44b128e59b854 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/11160 Reviewed-by: David Turner <digit@google.com> Reviewed-by: Austin Eng <enga@chromium.org> Commit-Queue: Corentin Wallez <cwallez@chromium.org>
2019-09-11 16:53:46 +00:00
# Just skip GLFW on other systems
Enable Vulkan for Chromium Fuchsia build. Enable the Vulkan backend when building Dawn with the Chromium build system for Fuchsia. To make this work properly the following is required: - Modify VulkanInfo.cpp and BackendVk.cpp to correctly probe the Fuchsia swapchain layer and its layer extension, as well as enabling them when creating a new VkInstance. - Modify VulkanFunctions.cpp to load the Fuchsia swapchain related extension for this platform only. - Provide a small mock GLFW library for Fuchsia under src/utils/Glfw3Fuchsia.cpp, since the upstream project does not support this platform at all. Its purpose is only to allow the creation of the right VulkanBinding instance, which depends on the creation of a display surface for latter swapchain creation. - Add //third_party/fuchsia-sdk:vulkan_base and //third_party/fuchsia-sdk:vulkan_validation as da