| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
| |
protos from linking into the final binary.
--
MOS_MIGRATED_REVID=134409481
|
|
|
|
|
|
|
|
|
| |
These changes could help use build TensorFlow on Windows
--
Change-Id: I98962add450da234d5965b091607817e991af383
Reviewed-on: https://bazel-review.googlesource.com/#/c/6270
MOS_MIGRATED_REVID=134266671
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=134110312
|
|
|
|
|
|
|
| |
md5 repeatedly from bash is too slow.
--
MOS_MIGRATED_REVID=134087524
|
|
|
|
|
|
|
| |
bazel after commit 1092e9d68773adb7444cc85a47af650aeeaf65fc
--
MOS_MIGRATED_REVID=134036851
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
**Experimental**
This is an initial implementation of the maven_jar rule in Skylark, targeted at
the FRs in issue #1410.
Implemented a wrapper around the maven binary to pull dependencies from
remote repositories into a directory under {output_base}/external.
Attributes `name`, `artifact`, `repository`, `sha1` have been implemented,
but not `server`.
Caveat: this rule assumes that the Maven dependency is installed in the
system. Hence, the maven_skylark_test integration tests are tagged with
"manual" and commented out because the Bazel CI isn't configured with
the Maven binary yet.
Added a serve_not_found helper for 404 response tests.
Usage:
```
load("@bazel_tools//tools/build_defs/repo:maven_rules.bzl", "maven_jar")
maven_jar(
name = "com_google_guava_guava",
artifact = "com.google.guava:guava:18.0",
sha1 = "cce0823396aa693798f8882e64213b1772032b09",
repository = "http://uk.maven.org/maven2",
)
```
With regards to server, there are some limitations with retrieving a
maven_server's attribute at Loading Phase without the use of hacky macros
(issue #1704), and even if macros are used, the maven_server is not treated as
an actual dependency by maven_jar. There is a test (`test_unimplemented_server_attr`)
to ensure that the error message to shown to users if they use the server
attribute with this rule.
--
Change-Id: I167f9d13835c30be971928b4cc60167a8e396893
Reviewed-on: https://bazel-review.googlesource.com/c/5770
MOS_MIGRATED_REVID=133971809
|
|
|
|
|
|
|
| |
* Removes iOS specific platform/cpu calls in favor of platform-agnostic counterparts.
--
MOS_MIGRATED_REVID=133966024
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133847278
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133752908
|
|
|
|
|
|
|
| |
xcode not being installed), create a stub xcode_version target instead of a malformed one.
--
MOS_MIGRATED_REVID=133709696
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133693782
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133629682
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133618837
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133436157
|
|
|
|
|
|
|
| |
* Also rename the partial swift module outputs so they don't clash with final modules.
--
MOS_MIGRATED_REVID=133410717
|
|
|
|
|
|
|
| |
Previously, zip_manifest_creator.sh would return an exit code of 1 if grep did not match any files.
--
MOS_MIGRATED_REVID=133289788
|
|
|
|
|
|
|
|
|
|
| |
In case cc_configure finds the wrong bash binary if user is running Windows 10 with bash on Windows.
This should help https://github.com/bazelbuild/bazel/issues/1453
--
Change-Id: Iffd365e3e2dd2389882390dffdf6f3a88719530e
Reviewed-on: https://bazel-review.googlesource.com/#/c/6072
MOS_MIGRATED_REVID=133270634
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently only uses AndroidManifest.xml, classes.jar and res/ from AARs. This is sufficient for many of the AARs of Google Play Services and Android Support Repository.
The next step will be for AndroidSdkRepositoryRule to scan the SDK and generate aar_import rules for the AARs within.
The rule is not yet documented because it is not intended for end users to use it yet. We should probably support more of the features of AARs before that time. See http://tools.android.com/tech-docs/new-build-system/aar-format for all of the files that can be included in AARs.
Also note that R.txt from the AAR is intentionally ignored and regenerated based on the contents of res/. This is more correct, because the R.txt inside of an AAR can contain ids for dependencies of the AAR that are not included in res/.
See https://github.com/bazelbuild/bazel/issues/564 for discussion of supporting AARs and https://github.com/bazelbuild/bazel/issues/1745 for motivation to get it done soon.
--
MOS_MIGRATED_REVID=133127933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main motivations for this are:
* This makes the load label for the Skylark git rules cleaner.
* I am planning to add similar rules, such as hg.bzl, in the future.
Tagging #1408 for FYI
RELNOTES: Move Skylark git_repository rules to git.bzl
--
MOS_MIGRATED_REVID=133094634
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=133045120
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks all projects using Bazel, see https://ci.bazel.io
*** Original change description ***
Deprecated and removed HOST_CFG and DATA_CFG global variables.
--
MOS_MIGRATED_REVID=133005398
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132976702
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is using printf-style formatting, which Python happily accepts and
ignores.
Part of #1750: now, instead of printing
```
xcode_configure.bzl:57:5: Invoking xcodebuild failed, return code %s,
stderr: %s 1
```
it prints:
```
xcode_configure.bzl:57:5: Invoking xcodebuild failed, return code 1,
stderr: xcrun: error: missing DEVELOPER_DIR path: E.g. no application
claims the file"
```
Closes #1751.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1751
MOS_MIGRATED_REVID=132884125
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132675557
|
|
|
|
|
|
|
| |
Fixed #1736
--
MOS_MIGRATED_REVID=132529145
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132458460
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132436354
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132422029
|
|
|
|
|
|
|
| |
RELNOTES: swift_library can be used to build watchOS apps.
--
MOS_MIGRATED_REVID=132355955
|
|
|
|
|
|
|
|
|
|
| |
BSD sed (the default on osx) does not support the -r --regexp-extended flag. Fixes #1651
Closes #1716.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1716
MOS_MIGRATED_REVID=132350276
|
|
|
|
|
|
|
|
|
|
|
| |
The docker version command does not have a format flag until Docker 1.8,
so if it exits with a non zero exit code default to Docker version 1.5
instead of 1.10.
--
Change-Id: I971bb0d8d0108e4bb6076710be5e9dfe1893e472
Reviewed-on: https://bazel-review.googlesource.com/#/c/5771
MOS_MIGRATED_REVID=132341532
|
|
|
|
|
|
|
|
|
| |
filegroup to declare C++ toolchains.
Tested by actually removing support for filegroups; it's a ~5-line change, but it's better to do that separately so that it can be rolled back easily if need be.
--
MOS_MIGRATED_REVID=132320198
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Any java rule that mixes generated and non-generated sources
will produce a filtered jar containing only the generated
output.
For a java rule with only "normal" sources or only generated
source files, no filtered jar is produced.
This will allow the IDE to resolve those generated sources.
RELNOTES:None
--
MOS_MIGRATED_REVID=132113568
|
|
|
|
|
|
|
|
|
|
| |
the embedded_tools repo.
Do not submit until https://bazel-review.googlesource.com/#/c/5630/6 is merged.
Also do not submit until unknown commit goes in.
--
MOS_MIGRATED_REVID=131950953
|
|
|
|
|
|
|
|
|
| |
These two Skylark symbols are functions, not variables. I attempted to
correct the references to match the symbol type, but I cannot get the
tests to fully pass -- so better disable this until properly fixed.
--
MOS_MIGRATED_REVID=131942175
|
|
|
|
|
|
|
|
| |
Improve build determinism by squashing timestamps.
-) Set ZERO_AR_DATE for ar invocations.
--
MOS_MIGRATED_REVID=131861235
|
|
|
|
|
|
|
|
|
|
|
| |
of xcode to select between, relaxing the requirement that users specify --xcode_version and --ios_sdk_version even if they have only one version installed.
RELNOTES: On mac devices, detect locally installed versions of xcode to:
1. Use a sensible default if xcode is required but --xcode_version is unspecified.
2. Use sensible default iOS SDK version for the targeted version of xcode if ios_sdk_version is unspecified.
--
MOS_MIGRATED_REVID=131841587
|
|
|
|
|
|
|
| |
--
Change-Id: Ib2066597f3aeec2b160dd56fd19c60d618cb925d
Reviewed-on: https://bazel-review.googlesource.com/#/c/4280
MOS_MIGRATED_REVID=131699503
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=131631222
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part 3 of the 3 new proposed android_library res
processing actions. Pulls a zip file from the
merging action, unpacks it, and then validates
the results with aapt. Get an R.txt and srcjar
w/ javadocs from aapt. In order to the get the
R.txt, I think you need to ask for the R.java
sources anyway.
Split the processResources() into a runAapt()
function that can be reused.
Hookup in bazel coming separately.
--
MOS_MIGRATED_REVID=131618410
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part 2 of the 3 new proposed android_library res
processing actions. The primary and deps are all
assumed to be parsed+summarized in a protobuf.
Represent that with a new class (similar to
DependencyAndroidData but w/out R.txt).
Avoid having "manifest" artifacts as deps input,
and instead use "label", since that is only used
in a warning. DepAD still uses the manifest for
#asSymbolFileProvider, so we keep it there.
Move loading the primary out of the merge function
so that we can share the merge function with this
style of primary data, and the existing style of
of primary data (UnvalidatedAndroidData).
This produces an R class.jar and a zip file to
pass along to a future validation action. Images
are stubbed out since they are irrelevant to the
validation action.
--
MOS_MIGRATED_REVID=131604421
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pkg_deb can have either conffiles or conffiles_file parameter that propagates
the list of conffiles into the deb archive.
Also the tests in //tools/build_defs/pkg were fixed to run against the rules
from the source tree and not from the bazel distribtution.
--
Change-Id: I61c447feef16511acbb0078d91954dcd7d3375f4
Reviewed-on: https://bazel-review.googlesource.com/#/c/5610
MOS_MIGRATED_REVID=131391925
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old manifest merger doesn't merge xmlns decls.
That could be a problem if a library has xmlns:tools
but the binary doesn't (and we don't strip tools:).
Library manifests may end up with more xmlns:tools
annotations while transitioning from the old manifest
merger to the new. It would be a problem if the same
manifest is used by both the old and new merger.
An alternative may be to strip the tools annotations
after merging w/ this old merger... other options?
--
MOS_MIGRATED_REVID=131332171
|
|
|
|
|
|
|
| |
--
Change-Id: If9b46439d0c0df36737030c9d78c201a87f1a4e9
Reviewed-on: https://bazel-review.googlesource.com/c/5590/
MOS_MIGRATED_REVID=131317750
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130938527
|
|
|
|
|
|
|
|
|
|
| |
This makes the same change to cc_configure.bzl made to the hard-coded
CROSSTOOL in 763f1397155fc7c12e1f1071a1bc942f91b867c4 to fix #1642
--
Change-Id: Ia05788243d0128ea4921f12c437ef6cebd83a4ff
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/5450/
MOS_MIGRATED_REVID=130636065
|
|
|
|
|
|
|
| |
The filegroup using this file was deleted in commit c9d4fae25137cf480e83566d992bef813fcad7ee
--
MOS_MIGRATED_REVID=130553843
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130549870
|
|
|
|
|
|
|
| |
* LLDB spawns an instance of Swift compiler under the hood, which is configured via command line flags recorded in DWARF at the time of compilation. In order for LLDB to properly import the module for the target being built, that command line has to provide a path to that module.
--
MOS_MIGRATED_REVID=130045157
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=129867284
|