GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
# Copyright 2016 Google Inc.
|
|
|
|
|
#
|
|
|
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
|
|
|
# found in the LICENSE file.
|
|
|
|
|
|
|
|
|
|
declare_args() {
|
|
|
|
|
}
|
|
|
|
|
|
2016-07-26 20:55:45 +00:00
|
|
|
skia_public_includes = [
|
|
|
|
|
"include/codec",
|
|
|
|
|
"include/config",
|
|
|
|
|
"include/core",
|
|
|
|
|
"include/effects",
|
|
|
|
|
"include/gpu",
|
|
|
|
|
"include/gpu/gl",
|
|
|
|
|
"include/images",
|
|
|
|
|
"include/pathops",
|
|
|
|
|
"include/ports",
|
|
|
|
|
"include/utils",
|
|
|
|
|
"include/utils/mac",
|
|
|
|
|
|
|
|
|
|
"include/c", # TODO: move back to top, order shouldn't matter
|
|
|
|
|
]
|
|
|
|
|
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
# Skia public API, generally provided by :skia.
|
|
|
|
|
config("skia_public") {
|
2016-07-26 20:55:45 +00:00
|
|
|
include_dirs = skia_public_includes
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
defines = [ "SKIA_DLL" ]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
# Skia internal APIs, used by Skia itself and a few test tools.
|
|
|
|
|
config("skia_private") {
|
|
|
|
|
visibility = [ ":*" ]
|
|
|
|
|
|
|
|
|
|
include_dirs = [
|
|
|
|
|
"include/private",
|
|
|
|
|
"src/c",
|
2016-07-26 20:55:45 +00:00
|
|
|
"src/codec",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
"src/config",
|
|
|
|
|
"src/core",
|
|
|
|
|
"src/effects",
|
|
|
|
|
"src/gpu",
|
|
|
|
|
"src/image",
|
|
|
|
|
"src/images",
|
|
|
|
|
"src/lazy",
|
|
|
|
|
"src/opts",
|
|
|
|
|
"src/pathops",
|
|
|
|
|
"src/ports",
|
|
|
|
|
"src/sfnt",
|
|
|
|
|
"src/utils",
|
|
|
|
|
"third_party/etc1",
|
|
|
|
|
"third_party/ktx",
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
# Any code that's linked into Skia-the-library should use this config via += skia_library_configs.
|
|
|
|
|
config("skia_library") {
|
|
|
|
|
visibility = [ ":*" ]
|
|
|
|
|
defines = [ "SKIA_IMPLEMENTATION=1" ]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
skia_library_configs = [
|
|
|
|
|
":skia_public",
|
|
|
|
|
":skia_private",
|
|
|
|
|
":skia_library",
|
|
|
|
|
]
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
core_gypi = exec_script("gn/gypi_to_gn.py",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
[
|
|
|
|
|
rebase_path("gyp/core.gypi"),
|
|
|
|
|
"--replace=<(skia_include_path)=include",
|
|
|
|
|
"--replace=<(skia_src_path)=src",
|
|
|
|
|
],
|
|
|
|
|
"scope",
|
|
|
|
|
[ "gyp/core.gypi" ])
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
effects_gypi = exec_script("gn/gypi_to_gn.py",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
[
|
|
|
|
|
rebase_path("gyp/effects.gypi"),
|
|
|
|
|
"--replace=<(skia_include_path)=include",
|
|
|
|
|
"--replace=<(skia_src_path)=src",
|
|
|
|
|
],
|
|
|
|
|
"scope",
|
|
|
|
|
[ "gyp/effects.gypi" ])
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
gpu_gypi = exec_script("gn/gypi_to_gn.py",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
[
|
|
|
|
|
rebase_path("gyp/gpu.gypi"),
|
|
|
|
|
"--replace=<(skia_include_path)=include",
|
|
|
|
|
"--replace=<(skia_src_path)=src",
|
|
|
|
|
],
|
|
|
|
|
"scope",
|
|
|
|
|
[ "gyp/gpu.gypi" ])
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
opts_gypi = exec_script("gn/gypi_to_gn.py",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
[
|
|
|
|
|
rebase_path("gyp/opts.gypi"),
|
|
|
|
|
"--replace=<(skia_include_path)=include",
|
|
|
|
|
"--replace=<(skia_src_path)=src",
|
|
|
|
|
],
|
|
|
|
|
"scope",
|
|
|
|
|
[ "gyp/opts.gypi" ])
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
pdf_gypi = exec_script("gn/gypi_to_gn.py",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
[
|
|
|
|
|
rebase_path("gyp/pdf.gypi"),
|
|
|
|
|
"--replace=<(skia_include_path)=include",
|
|
|
|
|
"--replace=<(skia_src_path)=src",
|
|
|
|
|
],
|
|
|
|
|
"scope",
|
|
|
|
|
[ "gyp/pdf.gypi" ])
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
utils_gypi = exec_script("gn/gypi_to_gn.py",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
[
|
|
|
|
|
rebase_path("gyp/utils.gypi"),
|
|
|
|
|
"--replace=<(skia_include_path)=include",
|
|
|
|
|
"--replace=<(skia_src_path)=src",
|
|
|
|
|
],
|
|
|
|
|
"scope",
|
|
|
|
|
[ "gyp/utils.gypi" ])
|
|
|
|
|
|
|
|
|
|
source_set("opts_ssse3") {
|
|
|
|
|
configs += skia_library_configs
|
|
|
|
|
|
|
|
|
|
sources = opts_gypi.ssse3_sources
|
|
|
|
|
cflags = [ "-mssse3" ]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
source_set("opts_sse41") {
|
|
|
|
|
configs += skia_library_configs
|
|
|
|
|
|
|
|
|
|
sources = opts_gypi.sse41_sources
|
|
|
|
|
cflags = [ "-msse4.1" ]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
source_set("opts_avx") {
|
|
|
|
|
configs += skia_library_configs
|
|
|
|
|
|
|
|
|
|
sources = opts_gypi.avx_sources
|
|
|
|
|
cflags = [ "-mavx" ]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
component("skia") {
|
|
|
|
|
public_configs = [ ":skia_public" ]
|
|
|
|
|
configs += skia_library_configs
|
|
|
|
|
|
|
|
|
|
deps = [
|
|
|
|
|
":opts_avx",
|
|
|
|
|
":opts_sse41",
|
|
|
|
|
":opts_ssse3",
|
2016-07-15 22:15:15 +00:00
|
|
|
"//third_party/zlib",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
]
|
|
|
|
|
|
2016-07-26 20:55:45 +00:00
|
|
|
defines = [
|
|
|
|
|
"SK_HAS_JPEG_LIBRARY",
|
|
|
|
|
"SK_HAS_PNG_LIBRARY",
|
|
|
|
|
]
|
|
|
|
|
|
2016-07-21 19:25:45 +00:00
|
|
|
libs = [ "pthread" ]
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
|
|
|
|
|
sources = []
|
|
|
|
|
sources += core_gypi.sources
|
|
|
|
|
sources += effects_gypi.sources
|
|
|
|
|
sources += gpu_gypi.skgpu_sources
|
|
|
|
|
sources += opts_gypi.sse2_sources
|
|
|
|
|
sources += pdf_gypi.sources
|
|
|
|
|
sources += utils_gypi.sources
|
|
|
|
|
sources += [
|
2016-07-26 20:55:45 +00:00
|
|
|
"src/codec/SkBmpCodec.cpp",
|
|
|
|
|
"src/codec/SkBmpMaskCodec.cpp",
|
|
|
|
|
"src/codec/SkBmpRLECodec.cpp",
|
|
|
|
|
"src/codec/SkBmpStandardCodec.cpp",
|
|
|
|
|
"src/codec/SkCodec.cpp",
|
|
|
|
|
"src/codec/SkCodecImageGenerator.cpp",
|
|
|
|
|
"src/codec/SkIcoCodec.cpp",
|
|
|
|
|
"src/codec/SkJpegCodec.cpp",
|
|
|
|
|
"src/codec/SkJpegDecoderMgr.cpp",
|
|
|
|
|
"src/codec/SkJpegUtility.cpp",
|
|
|
|
|
"src/codec/SkMaskSwizzler.cpp",
|
|
|
|
|
"src/codec/SkMasks.cpp",
|
|
|
|
|
"src/codec/SkPngCodec.cpp",
|
|
|
|
|
"src/codec/SkSampler.cpp",
|
|
|
|
|
"src/codec/SkSwizzler.cpp",
|
|
|
|
|
"src/codec/SkWbmpCodec.cpp",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
"src/images/SkImageEncoder.cpp",
|
|
|
|
|
"src/images/SkImageEncoder_Factory.cpp",
|
|
|
|
|
"src/ports/SkDiscardableMemory_none.cpp",
|
|
|
|
|
"src/ports/SkGlobalInitialization_default.cpp",
|
2016-07-26 20:55:45 +00:00
|
|
|
"src/ports/SkImageGenerator_skia.cpp",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
"src/ports/SkMemory_malloc.cpp",
|
|
|
|
|
"src/ports/SkOSFile_stdio.cpp",
|
|
|
|
|
"src/sfnt/SkOTTable_name.cpp",
|
|
|
|
|
"src/sfnt/SkOTUtils.cpp",
|
|
|
|
|
"src/utils/mac/SkStream_mac.cpp",
|
|
|
|
|
"third_party/etc1/etc1.cpp",
|
|
|
|
|
"third_party/ktx/ktx.cpp",
|
|
|
|
|
]
|
|
|
|
|
|
|
|
|
|
if (is_win) {
|
|
|
|
|
sources += [
|
|
|
|
|
"src/ports/SkDebug_win.cpp",
|
|
|
|
|
"src/ports/SkFontHost_win.cpp",
|
|
|
|
|
"src/ports/SkFontMgr_win_dw.cpp",
|
|
|
|
|
"src/ports/SkFontMgr_win_dw_factory.cpp",
|
|
|
|
|
"src/ports/SkImageEncoder_WIC.cpp",
|
|
|
|
|
"src/ports/SkImageGeneratorWIC.cpp",
|
|
|
|
|
"src/ports/SkOSFile_win.cpp",
|
|
|
|
|
"src/ports/SkScalerContext_win_dw.cpp",
|
|
|
|
|
"src/ports/SkTLS_win.cpp",
|
|
|
|
|
"src/ports/SkTypeface_win_dw.cpp",
|
|
|
|
|
]
|
|
|
|
|
} else {
|
|
|
|
|
sources += [
|
|
|
|
|
"src/ports/SkDebug_stdio.cpp",
|
|
|
|
|
"src/ports/SkOSFile_posix.cpp",
|
|
|
|
|
"src/ports/SkTLS_pthread.cpp",
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (is_linux) {
|
|
|
|
|
deps += [
|
|
|
|
|
"third_party:fontconfig",
|
|
|
|
|
"third_party:freetype2",
|
|
|
|
|
"third_party:libjpeg-turbo",
|
|
|
|
|
"third_party:libpng",
|
|
|
|
|
]
|
|
|
|
|
sources += [
|
|
|
|
|
"src/fonts/SkFontMgr_fontconfig.cpp",
|
|
|
|
|
"src/images/SkJPEGImageEncoder.cpp",
|
|
|
|
|
"src/images/SkJPEGWriteUtility.cpp",
|
|
|
|
|
"src/images/SkPNGImageEncoder.cpp",
|
|
|
|
|
"src/ports/SkFontConfigInterface_direct.cpp",
|
|
|
|
|
"src/ports/SkFontConfigInterface_direct_factory.cpp",
|
|
|
|
|
"src/ports/SkFontHost_FreeType.cpp",
|
|
|
|
|
"src/ports/SkFontHost_FreeType_common.cpp",
|
|
|
|
|
"src/ports/SkFontHost_fontconfig.cpp",
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
if (is_mac) {
|
|
|
|
|
sources += [
|
|
|
|
|
"src/ports/SkFontHost_mac.cpp",
|
|
|
|
|
"src/ports/SkImageEncoder_CG.cpp",
|
|
|
|
|
"src/ports/SkImageGeneratorCG.cpp",
|
|
|
|
|
]
|
|
|
|
|
libs += [ "ApplicationServices.framework" ]
|
|
|
|
|
}
|
2016-07-15 22:15:15 +00:00
|
|
|
|
|
|
|
|
if (is_fuchsia) {
|
2016-07-19 13:03:22 +00:00
|
|
|
sources += [ "src/ports/SkFontMgr_empty_factory.cpp" ]
|
2016-07-15 22:15:15 +00:00
|
|
|
}
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
}
|
|
|
|
|
|
2016-07-26 20:55:45 +00:00
|
|
|
action("skia.h") {
|
|
|
|
|
script = "gn/echo_headers.py"
|
|
|
|
|
args = [ rebase_path("$target_gen_dir/skia.h", root_build_dir) ] +
|
|
|
|
|
rebase_path(skia_public_includes, root_build_dir)
|
|
|
|
|
outputs = [
|
|
|
|
|
"$target_gen_dir/skia.h",
|
|
|
|
|
]
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
executable("fiddle") {
|
|
|
|
|
include_dirs = [ "$target_gen_dir" ]
|
|
|
|
|
libs = [ "OSMesa" ]
|
|
|
|
|
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
sources = [
|
2016-07-26 20:55:45 +00:00
|
|
|
"tools/fiddle/draw.cpp",
|
|
|
|
|
"tools/fiddle/fiddle_main.cpp",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
]
|
|
|
|
|
deps = [
|
|
|
|
|
":skia",
|
2016-07-26 20:55:45 +00:00
|
|
|
":skia.h",
|
GN
What we've got here is a little GN MVP. It's lacking any knobs and doesn't yet build anything but libskia, zlib, libpng, and libjpeg-turbo. I've been hopping back and forth between Linux at work and Mac at home. These seem to be at least partially working, enough to build and run cmake/example.cpp.
The xcode backend seems to work. From here, we can start exploring how to handle other backends (cmake,Android make, Google3). There are a couple things I want to try:
- add another backend like vs or xcode to GN directly
- intercept via a custom toolchain
- reverse from ninja -t commands
That last option seems kind of fun.
This tries to piggyback on Chrome's GN setup as much as possible. Chrome's got quite a lot figured out, and we're basically required to do this if we want to have a single GN build system shareable by Chrome, our bots, and other clients.
This pulls in some new DEPS:
- build: Chrome's GN configuration, and much more
- buildtools: hashes for gn binary, pulled via hooks
- tools/clang: hashes for Chrome's clang, pulled via hooks into third_party/llvm-build
It additionally symlinks tools/gyp to third_party/externals/gyp. GN pulls some stuff from tools/gyp on Mac.
Have not yet tried building for Windows, Android, or iOS.
BUG=skia:
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2087593002
Committed: https://skia.googlesource.com/skia/+/1d8de594f126b9a80bd8f8fa2005e90faf3b5b17
Review-Url: https://codereview.chromium.org/2087593002
2016-06-23 17:29:30 +00:00
|
|
|
]
|
|
|
|
|
}
|
