bazel/rules_foreign_cc
2
0
Fork 0
mirror of https://github.com/bazel-contrib/rules_foreign_cc synced 2024-11-25 17:31:25 +00:00
Code Issues Releases Activity
rules_foreign_cc/examples/WORKSPACE

48 lines
1.2 KiB
Python
Raw Normal View History

Reorganize examples to be in a separate workspace (#188) * Reorganize examples to be in a separate workspace This will help to define native tools toolchains for examples * Remove examples-related part from main WORKSPACE file * Copy .bazelrc to the examples workspace. * correction for Bazel HEAD compatibility * Changes to run nested workspace tests from main workspace
2019-01-07 09:31:27 +00:00
workspace(name = "rules_foreign_cc_tests")
local_repository(
name = "rules_foreign_cc",
path = "..",
)
load("@rules_foreign_cc//:workspace_definitions.bzl", "rules_foreign_cc_dependencies")
Extract cmake and ninja into a toolchain; provide defaults. (#192) * Extract cmake and ninja into a toolchain; provide defaults. In the workspace-level rule registration function, default toolchain implementations are registered for all platforms, which are calling the cmake and ninja just by name, assuming they are preinstalled. Also, the user can pass the custom toolchains in the initialization function, they will be registered before the defaults. * Do not run ninja build test for now without nested workspaces support * Corrections after merge * Always build ninja from sources for tests, correct initialization order * Add example of using prebuilt artefact in the native tools toolchain. * Review comments, have native_tool_toolchain#target, not label + improve documentation * Correct ninja toolchain label * Correct documentation in native_tools_toolchain.bzl
2019-01-08 11:25:16 +00:00
rules_foreign_cc_dependencies([
"//:built_cmake_toolchain",
Extract shell fragments into a toolchain (#196) * Extract shell fragments into a toolchain Construct script in framework.bzl using special notation for calling shell fragments, defining and referencing environment variables; have the script converted from this special notation into a real script (see README.md notes.) The special notation is used to keep script construction in code still readable. Tools scripts (cmake, ninja) were also converted. * Fix reference to environment variables in examples .. and reference it correctly $$var_name$$ so it is replaced further * Review comments: documentation, explicitly mark functions from toolchain - mark functions from shell toolchain as ##funname##, so that they can not be mixed with usual shell functions * Fix operating system name for windows in toolchain file * Additional env vars for windows * Correct cmake tool build * Do not build ninja on Windows * When run on Windows under msys, find utility from Window could "leak"... into the script. Use heuristics to use /usr/bin/find if it exists. Also, use pwd -W to get Windows-styled paths (for cmake)
2019-01-18 17:06:10 +00:00
"//:built_ninja_toolchain_osx",
"//:built_ninja_toolchain_linux",
Extract cmake and ninja into a toolchain; provide defaults. (#192) * Extract cmake and ninja into a toolchain; provide defaults. In the workspace-level rule registration function, default toolchain implementations are registered for all platforms, which are calling the cmake and ninja just by name, assuming they are preinstalled. Also, the user can pass the custom toolchains in the initialization function, they will be registered before the defaults. * Do not run ninja build test for now without nested workspaces support * Corrections after merge * Always build ninja from sources for tests, correct initialization order * Add example of using prebuilt artefact in the native tools toolchain. * Review comments, have native_tool_toolchain#target, not label + improve documentation * Correct ninja toolchain label * Correct documentation in native_tools_toolchain.bzl
2019-01-08 11:25:16 +00:00
])
Reorganize examples to be in a separate workspace (#188) * Reorganize examples to be in a separate workspace This will help to define native tools toolchains for examples * Remove examples-related part from main WORKSPACE file * Copy .bazelrc to the examples workspace. * correction for Bazel HEAD compatibility * Changes to run nested workspace tests from main workspace
2019-01-07 09:31:27 +00:00
Windows, tests: fix for native test wrapper (#246) * Windows, tests: fix for native test wrapper In this PR: - Update `@bazel_skylib` to 0.8.0, which has a Windows-compatible unittest.bzl - Fix unittest-using tests. Correct usage of `unittest.end(env)` is to return its value. Result: //test:all now passes with Bazel 0.25.0rc3 and --incompatible_windows_native_test_wrapper * Register Skylib toolchains * rules_foreign_cc_dep registers unittest toolchains * Address review comments * Add bazel_skylib_workspace to WORKSPACE files * Remove stale toolchain init code
2019-04-30 13:50:26 +00:00
load("@bazel_skylib//:workspace.bzl", "bazel_skylib_workspace")
bazel_skylib_workspace()
Reorganize examples to be in a separate workspace (#188) * Reorganize examples to be in a separate workspace This will help to define native tools toolchains for examples * Remove examples-related part from main WORKSPACE file * Copy .bazelrc to the examples workspace. * correction for Bazel HEAD compatibility * Changes to run nested workspace tests from main workspace
2019-01-07 09:31:27 +00:00
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
android_sdk_repository(
name = "androidsdk",
)
android_ndk_repository(
name = "androidndk",
)
Fix Buildkite breakage caused by gmaven_rules rename (#236) * Fix buildkite breakage * update examples WORKSPACE
2019-03-12 14:41:04 +00:00
# TODO(jin): replace legacy gmaven_rules targets with `maven_install` from the new rules_jvm_external
RULES_JVM_EXTERNAL_TAG = "1.0"
RULES_JVM_EXTERNAL_SHA = "48e0f1aab74fabba98feb8825459ef08dcc75618d381dff63ec9d4dd9860deaa"
Reorganize examples to be in a separate workspace (#188) * Reorganize examples to be in a separate workspace This will help to define native tools toolchains for examples * Remove examples-related part from main WORKSPACE file * Copy .bazelrc to the examples workspace. * correction for Bazel HEAD compatibility * Changes to run nested workspace tests from main workspace
2019-01-07 09:31:27 +00:00
http_archive(
name = "gmaven_rules",
Fix Buildkite breakage caused by gmaven_rules rename (#236) * Fix buildkite breakage * update examples WORKSPACE
2019-03-12 14:41:04 +00:00
strip_prefix = "rules_jvm_external-%s" % RULES_JVM_EXTERNAL_TAG,
sha256 = RULES_JVM_EXTERNAL_SHA,
url = "https://github.com/bazelbuild/rules_jvm_external/archive/%s.zip" % RULES_JVM_EXTERNAL_TAG,
Reorganize examples to be in a separate workspace (#188) * Reorganize examples to be in a separate workspace This will help to define native tools toolchains for examples * Remove examples-related part from main WORKSPACE file * Copy .bazelrc to the examples workspace. * correction for Bazel HEAD compatibility * Changes to run nested workspace tests from main workspace
2019-01-07 09:31:27 +00:00
)
load("@gmaven_rules//:gmaven.bzl", "gmaven_rules")
gmaven_rules()
load(":examples_repositories.bzl", "include_examples_repositories")
include_examples_repositories()
Copy permalink