| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124565078
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124560388
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
MOS_MIGRATED_REVID=124556360
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124556005
|
|
|
|
|
|
|
|
|
| |
error when the LIPO context is not a cc_binary.
RELNOTES[NEW]: LIPO context (--lipo_context) can now also be a cc_test (in addition to cc_binary)
--
MOS_MIGRATED_REVID=124555465
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
MOS_MIGRATED_REVID=124553522
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124551962
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
MOS_MIGRATED_REVID=124549894
|
|
|
|
|
|
|
| |
Fixes #1310.
--
MOS_MIGRATED_REVID=124548907
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
--
MOS_MIGRATED_REVID=124548575
|
|
|
|
|
|
|
| |
Fixes #31.
--
MOS_MIGRATED_REVID=124545704
|
|
|
|
|
|
|
|
|
|
| |
This is no longer maintained and is now replaced by e4b:
https://github.com/bazelbuild/e4b
Fixes #12.
--
MOS_MIGRATED_REVID=124545211
|
|
|
|
|
|
|
| |
--
Change-Id: I2f08a61c06a1a6fda6a8e30c347cca3336b01b95
Reviewed-on: https://bazel-review.googlesource.com/#/c/3780
MOS_MIGRATED_REVID=124544524
|
|
|
|
|
|
|
| |
See https://groups.google.com/d/msgid/bazel-discuss/CAM01fBriKWxwFeb%2B-M80ryJq2Um97N9JZbr5BF7pO-xVa8cL_g%40mail.gmail.com?utm_medium=email&utm_source=footer
--
MOS_MIGRATED_REVID=124543258
|
|
|
|
|
|
|
| |
and "Bazel Test Encyclopedia" externally.
--
MOS_MIGRATED_REVID=124540293
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: a9301fa
Cherry picks:
+ ff30a73: Turn --legacy_external_runfiles back on by default
+ aeee3b8: Fix delete[] warning on fsevents.cc
Incompatible changes:
- The --cwarn command line option is not supported anymore. Use
--copt instead.
New features:
- On OSX, --watchfs now uses FsEvents to be notified of changes
from the filesystem (previously, this flag had no effect on OS X).
- add support for the '-=', '*=', '/=', and'%=' operators to
skylark. Notably, we do not support '|=' because the semantics
of skylark sets are sufficiently different from python sets.
Important changes:
- Use singular form when appropriate in blaze's test result summary
message.
- Added supported for Android NDK revision 11
- --objc_generate_debug_symbols is now deprecated.
- swift_library now generates an Objective-C header for its @objc
interfaces.
- new_objc_provider can now set the USES_SWIFT flag.
- objc_framework now supports dynamic frameworks.
- Symlinks in zip files are now unzipped correctly by http_archive,
download_and_extract, etc.
- swift_library is now able to import framework rules such as
objc_framework.
- Adds "jre_deps" attribute to j2objc_library.
- Release apple_binary rule, for creating multi-architecture
("fat") objc/cc binaries and libraries, targeting ios platforms.
- Aspects documentation added.
- The --ues_isystem_for_includes command line option is not
supported anymore.
- global function 'provider' is removed from .bzl files. Providers
can only be accessed through fields in a 'target' object.
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124510100
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124487512
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124483721
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124481285
|
|
|
|
|
|
|
| |
instead load it from //external.
--
MOS_MIGRATED_REVID=124480945
|
|
|
|
|
|
|
|
| |
The @SkylarkCallable annotation is very limited and to extend it
it is best to share a similar API than the @SkylarkSignature annotation.
--
MOS_MIGRATED_REVID=124473056
|
|
|
|
|
|
|
|
|
|
| |
@SkylarkCallable and @SkylarkSignature were undocumented, making
it hard for the developer to understand these annotations.
This change add basic documentation for them.
--
MOS_MIGRATED_REVID=124461858
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124448791
|
|
|
|
|
|
|
|
|
|
|
|
| |
--nolegacy_external_runfiles breaks $(location @repo//) syntax for the runfiles case. This will be fixed when the structure of external repository in the execroot will be the same as in the runfiles tree so let flip that flag back on.
Fixes #1356.
RELNOTES: Revert of commit bd69849378112c3b05bc218e57cdafca82860710, legacy runfiles tree paths are still
supported by default.
--
MOS_MIGRATED_REVID=124445792
|
|
|
|
|
|
|
|
| |
This fixes the breakage caused by commit 828a9e2f167db8c4debca6e00ee37dd030849c2f
Also modified test to check options for generating dependency file.
--
MOS_MIGRATED_REVID=124441471
|
|
|
|
|
|
|
| |
preparation for there not being a unique target configuration.
--
MOS_MIGRATED_REVID=124439969
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a user is running a test with lots of runs (e.g., to debug flakyness),
it is useful to immediately see individual failures and not wait for the
summary of tests. Therefore, report failure events just like errors in the
scrollback buffer.
--
Change-Id: If32d1201f59cec75d99d18a50fc881c3596c3081
Reviewed-on: https://bazel-review.googlesource.com/#/c/3770
MOS_MIGRATED_REVID=124437705
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, analysis-time cycle detection expects all cycles to come from ConfiguredTargetFunction.
With dynamic configurations, ConfiguredTargetFunction calls out to TransitiveTargetFunction to figure out which configuration fragments its deps need.
If there's a cycle between the current target and a dep, the dep's TransitiveTargetFunction fails, which the current cycle detection code can't handle.
But even if it could handle it, since the failure occurs in the dep we'd get error messages like:
"in cc_library rule //the:dep: cycle in dependency graph"
instead of the expected:
"in cc_library rule //the:top_level_rule: cycle in dependency graph"
This used to not be a problem because loading-phase cycle detection caught the cycle before all this triggered. But interleaved loading and analysis removes that gate.
Tested: BuildViewTest cycle detection tests with dynamic configurations turned on
--
MOS_MIGRATED_REVID=124391277
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Makes it so module map generation action will be registered for all targets that should provide module maps. This allows other rules to depend directly on modulemap artifacts without turning on --experimental_objc_enable_module_maps for all builds.
* Disabled module maps for apple_binary because of a bug.
* objc_proto_library targets will register module map generation even with experimental union flag so that its modules can be imported by the dependent targets (even though the compilation is happening much later in the linking target).
RELNOTES:
--
MOS_MIGRATED_REVID=124386048
|
|
|
|
|
|
|
|
|
|
| |
don't yet support fragments from late-bound attributes.
This is intended to extend to any other class of errors that can't
already be centrally encoded somewhere in the production logic.
--
MOS_MIGRATED_REVID=124384937
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124381114
|
|
|
|
|
|
|
|
|
| |
versions and their aliases in easily-parsed format
This is convenient as skylark does not have extensive string-parsing (regex) features, and when xcode-locator is invoked from a skylark rule, this format is cleanest and contains only relevant info.
--
MOS_MIGRATED_REVID=124372740
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
AppleConfiguration.
Additionally, tweak single-architecture ios-platform logic such that ios_multi_cpus is checked before ios_cpu.
There are two contexts to note:
1. Single-architecture logic, (generally post-split), unaware of its own platform type aside
from configuration. This retrieves platform type from the --apple_platform_type configuration value.
a. getSingleArchPlatform() for Platform retrieval
b. getSingleArchitecture() for architecture retrieval
2. Multi-architecture logic, which should be aware of its own platform type, and passes it into
configuration accessors.
a. getMultiArchPlatform(PlatformType)
b. getMultiArchitectures(PlatformType)
All callers are migrated to these methods, though some still pass IOS platform type even though
they may need to be refactored to support additional platform types later.
--
MOS_MIGRATED_REVID=124370652
|
|
|
|
|
|
|
|
|
| |
args as a -filelist arg.
This prevents certain many-arg actions from making clang unhappy.
--
MOS_MIGRATED_REVID=124367172
|
|
|
|
|
|
|
| |
JavaLibraryHelper.
--
MOS_MIGRATED_REVID=124356892
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124356206
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124355936
|
|
|
|
|
|
|
|
|
| |
Also moved -S and -E options into the same action_config.
Since whoever consume CppCompileInfo add -c and -o options by themselves, to
keep compatible with this, the original code is still kept and used, until the corresponding flag sets are added into CROSSTOOL.
--
MOS_MIGRATED_REVID=124350905
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Docker 1.10 updated the format of images moving layers to just being
tarballs referenced by a configuration file. A new manifest.json file
aggregates images and handles parent and tagging references. Layers and
images are now identified by their sha256 hash. An image configuration
file must reference all layers that belong to it by this identifier,
including all layers in any parent images.
Image configuration is generated the same way but now allows multiple
layer sha256 hashes to be provided. The base image configuration is read
to find config defaults and the layer identifiers that need to be
present.
Image creation now requires the layer identifier and file and can accept
multiple layers. A manifest with a single entry is created that points
at the image configuration, its layers and tags. If a base image is
provided its layers are added to the begining of the layer section and a
parent reference to the base image is added. Multiple tags can be
provided which are applied when the image is loaded.
The joining of partial images now consists of merging their contents
minus the manifest which is concatentated together.
These changes have been made in a backwards compatible way so versions
of docker below 1.10 will still work as before.
Fixes #1113
--
Change-Id: I0075decc48d8846ad16431948192db196ad702ee
Reviewed-on: https://bazel-review.googlesource.com/3730
MOS_MIGRATED_REVID=124339578
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124338877
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=124338362
|
|
|
|
|
|
|
|
| |
Other option would be to just remove the html tags from inside the code-formatted string. Feel free to copy-paste and commit rather than accepting the PR.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1327
MOS_MIGRATED_REVID=124335824
|
|
|
|
|
|
|
|
|
| |
changed use_testrunner doc from mentioning non existent GoogleTestRunner to BazelTestRunner
fixes bazelbuild/bazel#1345
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1354
MOS_MIGRATED_REVID=124335414
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Java's Arrays.copyOfRange expects as "to" argument the index of the
first character not to be copied. As indices start with 0, the first
index outside the array is, in fact, the length itself (and not one
more than the length).
This off-by-one error so far never caused any problems, as Arrays.copyOfRange
is guaranteed to accept arbitrary large "to" values and helpfully
pads with 0-bytes. As 0-bytes are not shown on most terminals, the
output still looked correct. However, that off-by-one error did mess
up the output for users of the --experimental_show_artifacts flag.
--
Change-Id: I135ff720740db5c224a47668fc7513cbb7110f9f
Reviewed-on: https://bazel-review.googlesource.com/#/c/3771
MOS_MIGRATED_REVID=124332337
|
|
|
|
|
|
|
|
|
|
| |
SkylarkSignature
Those arrays were checked to never have more than one value so use an empty name
instead of the empty array. This simplify comprehension of the API.
--
MOS_MIGRATED_REVID=124330918
|
|
|
|
|
|
|
| |
Fixes #1347.
--
MOS_MIGRATED_REVID=124330246
|
|
|
|
|
|
|
|
| |
Fixes #1343 due to missing iOS SDK version.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1350
MOS_MIGRATED_REVID=124328836
|
|
|
|
|
|
|
| |
/bin/bash is always wrong on windows.
--
MOS_MIGRATED_REVID=124273700
|
|
|
|
|
|
|
| |
after the Package is fully loaded.
--
MOS_MIGRATED_REVID=124260910
|