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

912 lines
28 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.
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
import("scripts/dawn_overrides_with_defaults.gni")
BUILD.gn: Move last third_party deps to third_party/BUILD.gn
2018-08-13 06:31:17 +00:00
import("scripts/dawn_features.gni")
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
import("//testing/test.gni")
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
###############################################################################
BUILD.gn: Use idiomatic string substitution
2018-08-03 12:01:35 +00:00
# Template to wrap the Dawn code generator
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +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
# Template to help with invocation of the Dawn code generator, looks like this:
#
# dawn_generator("my_target_gen") {
# # Which generator target to output
# target = "my_target"
# # The list of expected outputs, generation fails if there's a mismatch
# outputs = [
# "MyTarget.cpp",
# "MyTarget.h",
# ]
# }
#
# Using the generated files is done like so:
#
# shared_library("my_target") {
# deps = [ ":my_target_gen "]
# sources = get_target_outputs(":my_target_gen")
# }
#
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
template("dawn_generator") {
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
# The base arguments for the generator: from this dawn.json, generate this
# target using templates in this directory.
generator_args = [
rebase_path("dawn.json", root_build_dir),
Generator,BUILD.gn: add optional python path, use it for Jinja2 This makes the Jinja2 (and MarkupSafe) installation hermetic by adding it to the DEPS and making the code generator add them in the first spot of the python path.
2018-08-13 15:47:44 +00:00
"--template-dir",
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
rebase_path("generator/templates", root_build_dir),
"--targets",
invoker.target,
]
# Use the Jinja2 version pulled from the DEPS file. We do it so we don't
# have version problems, and users don't have to install Jinja2.
jinja2_python_path = rebase_path("${dawn_jinja2_dir}/..")
generator_args += [
Generator,BUILD.gn: add optional python path, use it for Jinja2 This makes the Jinja2 (and MarkupSafe) installation hermetic by adding it to the DEPS and making the code generator add them in the first spot of the python path.
2018-08-13 15:47:44 +00:00
"--extra-python-path",
jinja2_python_path,
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +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
# For build parallelism GN wants to know the exact inputs and outputs of
# action targets like we use for our code generator. We avoid asking the
# generator about its inputs by using the "depfile" feature of GN/Ninja.
#
# A ninja limitation is that the depfile is a subset of Makefile that can
# contain a single target, so we output a single "JSON-tarball" instead.
json_tarball = "${target_gen_dir}/${target_name}.json_tarball"
json_tarball_depfile = "${json_tarball}.d"
generator_args += [
"--output-json-tarball",
rebase_path(json_tarball, root_build_dir),
"--depfile",
rebase_path(json_tarball_depfile, root_build_dir),
]
# After the JSON tarball is created we need an action target to extract it
# with a list of its outputs. The invoker provided a list of expected
# outputs. To make sure the list is in sync between the generator and the
# build files, we write it to a file and ask the generator to assert it is
# correct.
expected_outputs_file = "${target_gen_dir}/${target_name}.expected_outputs"
write_file(expected_outputs_file, invoker.outputs)
generator_args += [
"--expected-outputs-file",
rebase_path(expected_outputs_file, root_build_dir),
]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +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
# The code generator invocation that will write the JSON tarball, check the
# outputs are what's expected and write a depfile for Ninja.
action("${target_name}_json_tarball") {
script = "generator/main.py"
outputs = [
json_tarball,
]
depfile = json_tarball_depfile
args = generator_args
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +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
# Extract the JSON tarball into the target_gen_dir
action("${target_name}") {
script = "generator/extract_json.py"
args = [
rebase_path(json_tarball, root_build_dir),
rebase_path(target_gen_dir, root_build_dir),
]
deps = [
":${target_name}_json_tarball",
]
inputs = [
json_tarball,
]
# The expected output list is relative to the target_gen_dir but action
# target outputs are from the root dir so we need to rebase them.
outputs = []
foreach(source, invoker.outputs) {
outputs += [ "${target_gen_dir}/${source}" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
}
}
}
###############################################################################
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
# Common dawn libraries and configs
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
###############################################################################
config("libdawn_public") {
include_dirs = [
target_gen_dir,
"src/include",
]
}
config("dawn_internal") {
include_dirs = [ "src" ]
defines = []
if (dawn_always_assert || is_debug) {
defines += [ "DAWN_ENABLE_ASSERTS" ]
}
if (dawn_enable_d3d12) {
defines += [ "DAWN_ENABLE_BACKEND_D3D12" ]
}
if (dawn_enable_metal) {
defines += [ "DAWN_ENABLE_BACKEND_METAL" ]
}
if (dawn_enable_null) {
defines += [ "DAWN_ENABLE_BACKEND_NULL" ]
}
if (dawn_enable_opengl) {
defines += [ "DAWN_ENABLE_BACKEND_OPENGL" ]
}
if (dawn_enable_vulkan) {
defines += [ "DAWN_ENABLE_BACKEND_VULKAN" ]
}
configs = [ ":libdawn_public" ]
Add samples to BUILD.gn and their deps to DEPS Also add missing GLFW DEPS entry
2018-08-13 06:23:27 +00:00
# Only internal Dawn targets can use this config, this means only targets in
# this BUILD.gn file.
visibility = [ ":*" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
}
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
# Executable needs an rpath to find our shared libraries on OSX
config("dawn_shared_library_public") {
if (is_mac) {
ldflags = [
"-rpath",
"@executable_path/",
]
}
}
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
static_library("dawn_common") {
sources = [
"src/common/Assert.cpp",
"src/common/Assert.h",
"src/common/BitSetIterator.h",
"src/common/Compiler.h",
"src/common/DynamicLib.cpp",
"src/common/DynamicLib.h",
"src/common/HashUtils.h",
"src/common/Math.cpp",
"src/common/Math.h",
"src/common/Platform.h",
"src/common/Result.h",
"src/common/Serial.h",
"src/common/SerialQueue.h",
"src/common/SwapChainUtils.h",
"src/common/vulkan_platform.h",
"src/common/windows_with_undefs.h",
]
configs += [ ":dawn_internal" ]
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
deps = [
":dawn_headers",
]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
}
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
###############################################################################
# Dawn headers and libdawn.so
###############################################################################
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
dawn_generator("dawn_headers_gen") {
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
target = "dawn_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
outputs = [
"dawn/dawncpp.h",
"dawn/dawn.h",
"dawn/dawncpp_traits.h",
]
}
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +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
source_set("dawn_headers") {
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
public_configs = [ ":libdawn_public" ]
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
deps = [
":dawn_headers_gen",
]
sources = get_target_outputs(":dawn_headers_gen")
sources += [
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
"src/include/dawn/EnumClassBitmasks.h",
"src/include/dawn/dawn_export.h",
"src/include/dawn/dawn_wsi.h",
]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +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
dawn_generator("libdawn_gen") {
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
target = "libdawn"
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 = [
"dawn/dawncpp.cpp",
"dawn/dawn.c",
]
}
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +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
shared_library("libdawn") {
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
public_deps = [
":dawn_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
defines = [ "DAWN_IMPLEMENTATION" ]
deps = [
":libdawn_gen",
]
sources = get_target_outputs(":libdawn_gen")
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
# Tell dependents where to find this shared library
if (is_mac) {
ldflags = [
"-install_name",
"@rpath/${target_name}.dylib",
]
public_configs = [ ":dawn_shared_library_public" ]
}
}
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
###############################################################################
# libdawn_native.so
###############################################################################
config("libdawn_native_internal") {
configs = [ ":dawn_internal" ]
defines = [ "DAWN_NATIVE_IMPLEMENTATION" ]
# Suppress warnings that Metal isn't in the deployment target of Chrome
if (is_mac) {
cflags_objcc = [ "-Wno-unguarded-availability" ]
}
}
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
dawn_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 = [
"dawn_native/ProcTable.cpp",
"dawn_native/dawn_structs_autogen.h",
"dawn_native/dawn_structs_autogen.cpp",
"dawn_native/ValidationUtils_autogen.h",
"dawn_native/ValidationUtils_autogen.cpp",
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
# Public libdawn_native headers so they can be publically visible for
# dependencies of libdawn_native
source_set("libdawn_native_headers") {
public_deps = [
":dawn_headers",
]
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
# shared_library / static_library / component versions of it.
source_set("libdawn_native_sources") {
deps = [
":dawn_common",
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",
BUILD.gn: Move last third_party deps to third_party/BUILD.gn
2018-08-13 06:31:17 +00:00
"third_party:spirv_cross",
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
# Put the internal config public so that unittests can see internal headers
public_configs = [ ":libdawn_native_internal" ]
# Set the headers as a public dependency so they are visible to unittests
public_deps = [
":libdawn_native_headers",
]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
libs = []
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 += [
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",
"src/dawn_native/BlendState.cpp",
"src/dawn_native/BlendState.h",
"src/dawn_native/Buffer.cpp",
"src/dawn_native/Buffer.h",
"src/dawn_native/Builder.cpp",
"src/dawn_native/Builder.h",
"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",
"src/dawn_native/Commands.cpp",
"src/dawn_native/Commands.h",
"src/dawn_native/ComputePipeline.cpp",
"src/dawn_native/ComputePipeline.h",
"src/dawn_native/DawnNative.cpp",
"src/dawn_native/DepthStencilState.cpp",
"src/dawn_native/DepthStencilState.h",
"src/dawn_native/Device.cpp",
"src/dawn_native/Device.h",
"src/dawn_native/Error.cpp",
"src/dawn_native/Error.h",
"src/dawn_native/ErrorData.cpp",
"src/dawn_native/ErrorData.h",
"src/dawn_native/Forward.h",
"src/dawn_native/InputState.cpp",
"src/dawn_native/InputState.h",
"src/dawn_native/PassResourceUsage.h",
"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",
"src/dawn_native/Queue.cpp",
"src/dawn_native/Queue.h",
"src/dawn_native/RefCounted.cpp",
"src/dawn_native/RefCounted.h",
"src/dawn_native/RenderPassDescriptor.cpp",
"src/dawn_native/RenderPassDescriptor.h",
"src/dawn_native/RenderPipeline.cpp",
"src/dawn_native/RenderPipeline.h",
"src/dawn_native/Sampler.cpp",
"src/dawn_native/Sampler.h",
"src/dawn_native/ShaderModule.cpp",
"src/dawn_native/ShaderModule.h",
"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",
"src/dawn_native/dawn_platform.h",
]
if (dawn_enable_d3d12) {
libs += [
"d3d12.lib",
"dxgi.lib",
Fix Windows compilation using GN and clang-cl. This includes a bunch of fixes for clang warnings in Windows specific code that was only compiled by MSVC previously. This also tidies up some BUILD.gn issues on Windows.
2018-08-13 15:50:22 +00:00
"dxguid.lib",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
"d3dcompiler.lib",
]
sources += [
"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/BlendStateD3D12.cpp",
"src/dawn_native/d3d12/BlendStateD3D12.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",
"src/dawn_native/d3d12/ComputePipelineD3D12.cpp",
"src/dawn_native/d3d12/ComputePipelineD3D12.h",
"src/dawn_native/d3d12/DepthStencilStateD3D12.cpp",
"src/dawn_native/d3d12/DepthStencilStateD3D12.h",
"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",
"src/dawn_native/d3d12/InputStateD3D12.cpp",
"src/dawn_native/d3d12/InputStateD3D12.h",
"src/dawn_native/d3d12/NativeSwapChainImplD3D12.cpp",
"src/dawn_native/d3d12/NativeSwapChainImplD3D12.h",
"src/dawn_native/d3d12/PipelineLayoutD3D12.cpp",
"src/dawn_native/d3d12/PipelineLayoutD3D12.h",
"src/dawn_native/d3d12/QueueD3D12.cpp",
"src/dawn_native/d3d12/QueueD3D12.h",
"src/dawn_native/d3d12/RenderPassDescriptorD3D12.cpp",
"src/dawn_native/d3d12/RenderPassDescriptorD3D12.h",
"src/dawn_native/d3d12/RenderPipelineD3D12.cpp",
"src/dawn_native/d3d12/RenderPipelineD3D12.h",
"src/dawn_native/d3d12/ResourceAllocator.cpp",
"src/dawn_native/d3d12/ResourceAllocator.h",
"src/dawn_native/d3d12/ResourceUploader.cpp",
"src/dawn_native/d3d12/ResourceUploader.h",
"src/dawn_native/d3d12/SamplerD3D12.cpp",
"src/dawn_native/d3d12/SamplerD3D12.h",
"src/dawn_native/d3d12/ShaderModuleD3D12.cpp",
"src/dawn_native/d3d12/ShaderModuleD3D12.h",
"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",
"src/dawn_native/d3d12/d3d12_platform.h",
]
}
if (dawn_enable_metal) {
libs += [
"Metal.framework",
"Cocoa.framework",
]
sources += [
"src/dawn_native/metal/BlendStateMTL.h",
"src/dawn_native/metal/BlendStateMTL.mm",
"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/DepthStencilStateMTL.h",
"src/dawn_native/metal/DepthStencilStateMTL.mm",
"src/dawn_native/metal/DeviceMTL.h",
"src/dawn_native/metal/DeviceMTL.mm",
"src/dawn_native/metal/Forward.h",
"src/dawn_native/metal/InputStateMTL.h",
"src/dawn_native/metal/InputStateMTL.mm",
"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/ResourceUploader.h",
"src/dawn_native/metal/ResourceUploader.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",
"src/dawn_native/metal/SwapChainMTL.h",
"src/dawn_native/metal/SwapChainMTL.mm",
"src/dawn_native/metal/TextureMTL.h",
"src/dawn_native/metal/TextureMTL.mm",
]
}
if (dawn_enable_null) {
sources += [
"src/dawn_native/null/NullBackend.cpp",
"src/dawn_native/null/NullBackend.h",
]
}
if (dawn_enable_opengl) {
BUILD.gn: Move last third_party deps to third_party/BUILD.gn
2018-08-13 06:31:17 +00:00
deps += [ "third_party:glad" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
sources += [
"src/dawn_native/opengl/BlendStateGL.cpp",
"src/dawn_native/opengl/BlendStateGL.h",
"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/DepthStencilStateGL.cpp",
"src/dawn_native/opengl/DepthStencilStateGL.h",
"src/dawn_native/opengl/DeviceGL.cpp",
"src/dawn_native/opengl/DeviceGL.h",
"src/dawn_native/opengl/Forward.h",
"src/dawn_native/opengl/InputStateGL.cpp",
"src/dawn_native/opengl/InputStateGL.h",
"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",
]
}
if (dawn_enable_vulkan) {
BUILD.gn: Move last third_party deps to third_party/BUILD.gn
2018-08-13 06:31:17 +00:00
deps += [ "third_party:vulkan_headers" ]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
sources += [
"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/BlendStateVk.cpp",
"src/dawn_native/vulkan/BlendStateVk.h",
"src/dawn_native/vulkan/BufferUploader.cpp",
"src/dawn_native/vulkan/BufferUploader.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",
"src/dawn_native/vulkan/ComputePipelineVk.cpp",
"src/dawn_native/vulkan/ComputePipelineVk.h",
"src/dawn_native/vulkan/DepthStencilStateVk.cpp",
"src/dawn_native/vulkan/DepthStencilStateVk.h",
"src/dawn_native/vulkan/DeviceVk.cpp",
"src/dawn_native/vulkan/DeviceVk.h",
"src/dawn_native/vulkan/FencedDeleter.cpp",
"src/dawn_native/vulkan/FencedDeleter.h",
"src/dawn_native/vulkan/Forward.h",
"src/dawn_native/vulkan/InputStateVk.cpp",
"src/dawn_native/vulkan/InputStateVk.h",
"src/dawn_native/vulkan/MemoryAllocator.cpp",
"src/dawn_native/vulkan/MemoryAllocator.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/RenderPassDescriptorVk.cpp",
"src/dawn_native/vulkan/RenderPassDescriptorVk.h",
"src/dawn_native/vulkan/RenderPipelineVk.cpp",
"src/dawn_native/vulkan/RenderPipelineVk.h",
"src/dawn_native/vulkan/SamplerVk.cpp",
"src/dawn_native/vulkan/SamplerVk.h",
"src/dawn_native/vulkan/ShaderModuleVk.cpp",
"src/dawn_native/vulkan/ShaderModuleVk.h",
"src/dawn_native/vulkan/SwapChainVk.cpp",
"src/dawn_native/vulkan/SwapChainVk.h",
"src/dawn_native/vulkan/TextureVk.cpp",
"src/dawn_native/vulkan/TextureVk.h",
"src/dawn_native/vulkan/VulkanFunctions.cpp",
"src/dawn_native/vulkan/VulkanFunctions.h",
"src/dawn_native/vulkan/VulkanInfo.cpp",
"src/dawn_native/vulkan/VulkanInfo.h",
]
}
}
# The shared library for libdawn_native for use by samples, tests, etc.
shared_library("libdawn_native") {
deps = [
":libdawn_native_sources",
]
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 initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
public_configs = [ ":libdawn_public" ]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
# Tell dependents where to find this shared library
if (is_mac) {
ldflags = [
"-install_name",
"@rpath/${target_name}.dylib",
]
public_configs += [ ":dawn_shared_library_public" ]
}
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
###############################################################################
# libdawn_wire.so
###############################################################################
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
# Public libdawn_wire headers so they can be publically visible for
# dependencies of libdawn_wire
source_set("libdawn_wire_headers") {
public_deps = [
":dawn_headers",
]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
sources = [
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
"src/include/dawn_wire/Wire.h",
"src/include/dawn_wire/dawn_wire_export.h",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +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
dawn_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 = [
"dawn_wire/WireServer.cpp",
"dawn_wire/WireCmd_autogen.h",
"dawn_wire/WireClient.cpp",
"dawn_wire/WireCmd_autogen.cpp",
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
]
}
shared_library("libdawn_wire") {
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
":dawn_common",
":libdawn_wire_gen",
":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
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
configs += [ ":dawn_internal" ]
defines = [ "DAWN_WIRE_IMPLEMENTATION" ]
sources = get_target_outputs(":libdawn_wire_gen")
sources += [ "src/dawn_wire/WireCmd.h" ]
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_wire_headers",
]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
public_configs = [ ":libdawn_public" ]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
# Tell dependents where to find this shared library
if (is_mac) {
ldflags = [
"-install_name",
"@rpath/${target_name}.dylib",
]
public_configs += [ ":dawn_shared_library_public" ]
}
}
###############################################################################
# Utils for tests and samples
###############################################################################
static_library("dawn_utils") {
configs += [ ":dawn_internal" ]
sources = [
"src/utils/BackendBinding.cpp",
"src/utils/BackendBinding.h",
"src/utils/DawnHelpers.cpp",
"src/utils/DawnHelpers.h",
"src/utils/SystemUtils.cpp",
"src/utils/SystemUtils.h",
"src/utils/TerribleCommandBuffer.cpp",
"src/utils/TerribleCommandBuffer.h",
]
deps = [
":dawn_common",
":libdawn_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
":libdawn_wire",
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
"third_party:glfw",
"third_party:libshaderc",
]
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
libs = []
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
if (dawn_enable_d3d12) {
sources += [ "src/utils/D3D12Binding.cpp" ]
}
if (dawn_enable_metal) {
sources += [ "src/utils/MetalBinding.mm" ]
libs += [
"Metal.framework",
"QuartzCore.framework",
]
# Suppress warnings that Metal isn't in the deployment target of Chrome
if (is_mac) {
cflags_objcc = [ "-Wno-unguarded-availability" ]
}
}
if (dawn_enable_null) {
sources += [ "src/utils/NullBinding.cpp" ]
}
if (dawn_enable_opengl) {
sources += [ "src/utils/OpenGLBinding.cpp" ]
BUILD.gn: Move last third_party deps to third_party/BUILD.gn
2018-08-13 06:31:17 +00:00
deps += [ "third_party:glad" ]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
}
if (dawn_enable_vulkan) {
sources += [ "src/utils/VulkanBinding.cpp" ]
BUILD.gn: Move last third_party deps to third_party/BUILD.gn
2018-08-13 06:31:17 +00:00
deps += [ "third_party:vulkan_headers" ]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
}
}
###############################################################################
# Dawn test targets
###############################################################################
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
dawn_generator("mock_dawn_gen") {
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
target = "mock_dawn"
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 = [
"mock/mock_dawn.h",
"mock/mock_dawn.cpp",
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
]
}
test("dawn_unittests") {
configs += [ ":dawn_internal" ]
if (is_linux) {
configs += [ "//build/config/gcc:rpath_for_built_shared_libraries" ]
}
deps = [
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
":dawn_common",
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
":dawn_headers",
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
":dawn_utils",
":libdawn",
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
":libdawn_native_sources",
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
":libdawn_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
":mock_dawn_gen",
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
"third_party:gmock",
"third_party:gtest",
]
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(":mock_dawn_gen")
sources += [
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
"src/tests/UnittestsMain.cpp",
"src/tests/unittests/BitSetIteratorTests.cpp",
"src/tests/unittests/CommandAllocatorTests.cpp",
"src/tests/unittests/EnumClassBitmasksTests.cpp",
"src/tests/unittests/ErrorTests.cpp",
"src/tests/unittests/MathTests.cpp",
"src/tests/unittests/ObjectBaseTests.cpp",
"src/tests/unittests/PerStageTests.cpp",
"src/tests/unittests/RefCountedTests.cpp",
"src/tests/unittests/ResultTests.cpp",
"src/tests/unittests/SerialQueueTests.cpp",
"src/tests/unittests/ToBackendTests.cpp",
"src/tests/unittests/WireTests.cpp",
"src/tests/unittests/validation/BindGroupValidationTests.cpp",
"src/tests/unittests/validation/BlendStateValidationTests.cpp",
"src/tests/unittests/validation/BufferValidationTests.cpp",
"src/tests/unittests/validation/CommandBufferValidationTests.cpp",
"src/tests/unittests/validation/ComputeValidationTests.cpp",
"src/tests/unittests/validation/CopyCommandsValidationTests.cpp",
"src/tests/unittests/validation/DepthStencilStateValidationTests.cpp",
"src/tests/unittests/validation/DynamicStateCommandValidationTests.cpp",
"src/tests/unittests/validation/InputStateValidationTests.cpp",
"src/tests/unittests/validation/PushConstantsValidationTests.cpp",
"src/tests/unittests/validation/RenderPassDescriptorValidationTests.cpp",
"src/tests/unittests/validation/RenderPipelineValidationTests.cpp",
"src/tests/unittests/validation/ValidationTest.cpp",
"src/tests/unittests/validation/ValidationTest.h",
"src/tests/unittests/validation/VertexBufferValidationTests.cpp",
]
if (dawn_enable_d3d12) {
Fix Windows compilation using GN and clang-cl. This includes a bunch of fixes for clang warnings in Windows specific code that was only compiled by MSVC previously. This also tidies up some BUILD.gn issues on Windows.
2018-08-13 15:50:22 +00:00
sources += [ "src/tests/unittests/d3d12/CopySplitTests.cpp" ]
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
}
}
test("dawn_end2end_tests") {
configs += [ ":dawn_internal" ]
if (is_linux) {
configs += [ "//build/config/gcc:rpath_for_built_shared_libraries" ]
}
deps = [
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
":dawn_common",
Add GN build for tests and their third party deps.
2018-08-03 13:57:43 +00:00
":dawn_utils",
":libdawn",
":libdawn_native",
":libdawn_wire",
"third_party:glfw",
"third_party:gtest",
]
sources = [
"src/tests/DawnTest.cpp",
"src/tests/DawnTest.h",
"src/tests/End2EndTestsMain.cpp",
"src/tests/end2end/BasicTests.cpp",
"src/tests/end2end/BlendStateTests.cpp",
"src/tests/end2end/BufferTests.cpp",
"src/tests/end2end/ComputeCopyStorageBufferTests.cpp",
"src/tests/end2end/CopyTests.cpp",
"src/tests/end2end/DepthStencilStateTests.cpp",
"src/tests/end2end/DrawElementsTests.cpp",
"src/tests/end2end/IndexFormatTests.cpp",
"src/tests/end2end/InputStateTests.cpp",
"src/tests/end2end/PrimitiveTopologyTests.cpp",
"src/tests/end2end/PushConstantTests.cpp",
"src/tests/end2end/RenderPassLoadOpTests.cpp",
"src/tests/end2end/SamplerTests.cpp",
"src/tests/end2end/ScissorTests.cpp",
"src/tests/end2end/ViewportOrientationTests.cpp",
]
Add initial BUILD.gn files for libdawn[|_native|_wire]
2018-07-31 16:50:03 +00:00
}
Add samples to BUILD.gn and their deps to DEPS Also add missing GLFW DEPS entry
2018-08-13 06:23:27 +00:00
###############################################################################
# Dawn samples, only in standalone builds
###############################################################################
if (dawn_standalone) {
# Static library to contain code and dependencies common to all samples
static_library("dawn_sample_utils") {
sources = [
"examples/SampleUtils.cpp",
"examples/SampleUtils.h",
]
# Export all of these as public deps so that `gn check` allows includes
public_deps = [
":dawn_common",
":dawn_utils",
":libdawn",
":libdawn_native",
":libdawn_wire",
"third_party:glfw",
]
public_configs = [ ":dawn_internal" ]
}
# Template for samples to avoid listing dawn_sample_utils as a dep every time
template("dawn_sample") {
executable(target_name) {
deps = [
":dawn_sample_utils",
]
forward_variables_from(invoker, "*", [ "deps" ])
if (defined(invoker.deps)) {
deps += invoker.deps
}
}
}
dawn_sample("CppHelloTriangle") {
sources = [
"examples/CppHelloTriangle.cpp",
]
}
dawn_sample("CHelloTriangle") {
sources = [
"examples/CHelloTriangle.cpp",
]
}
dawn_sample("ComputeBoids") {
sources = [
"examples/ComputeBoids.cpp",
]
deps = [
"third_party:glm",
]
}
dawn_sample("Animometer") {
sources = [
"examples/Animometer.cpp",
]
}
dawn_sample("CubeReflection") {
sources = [
"examples/CubeReflection.cpp",
]
deps = [
"third_party:glm",
]
}
dawn_sample("glTFViewer") {
sources = [
"examples/glTFViewer/Camera.inl",
"examples/glTFViewer/glTFViewer.cpp",
]
deps = [
"third_party:glm",
"third_party:tiny_gltf_loader",
]
}
}