skia2/WORKSPACE.bazel

load("@bazel_tools//tools/build_defs/repo:git.bzl", "new_git_repository")

new_git_repository(
    name = "libpng",
    remote = "https://skia.googlesource.com/third_party/libpng",
    #tag = "v1.6.37",
    commit = "a40189cf881e9f0db80511c382292a5604c3c3d1",
    shallow_since = "1555265432 -0400",
    build_file = "//bazel:libpng.bazel",
)
bazel baby steps A few first steps toward a Bazel build. To try it out, I think just $ bazel test ... I added third_party to .bazelignore to prevent Bazel from looking there. It can handle external dependencies itself, so no need to poke into what we sync from DEPS. Some of those have Bazel configs and we don't want to be building them yet. I've started by with libpng using new_git_repository(), mostly because it's small, with a mildly complex build, and needs dependencies of its own, zlib. Mysteriously zlib is built-in to Bazel, so that was easy. Next up is probably a dependency that does support Bazel, using git_repository(). That should make sure we can handle the full mix. Change-Id: I5775a1b254d341b9a90630aa1cc433a24167f2fd Reviewed-on: https://skia-review.googlesource.com/c/skia/+/316636 Commit-Queue: Mike Klein <mtklein@google.com> Reviewed-by: Joe Gregorio <jcgregorio@google.com> 2020-09-11 16:11:33 +00:00			`load("@bazel_tools//tools/build_defs/repo:git.bzl", "new_git_repository")`

			`new_git_repository(`
			`name = "libpng",`
			`remote = "https://skia.googlesource.com/third_party/libpng",`
			`#tag = "v1.6.37",`
			`commit = "a40189cf881e9f0db80511c382292a5604c3c3d1",`
			`shallow_since = "1555265432 -0400",`
			`build_file = "//bazel:libpng.bazel",`
			`)`