| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
As usual, README.md contains reproduction instructions.
It would be better to directly use the source tree under `boringssl.googlesource.com`, but for the time being, this will do.
Change-Id: I72ef030251c41eaed459c4abd93228f23223783b
|
|
|
|
| |
Motivation: 1.2 adds @AutoValue.Builder
|
|
|
|
|
|
|
|
| |
zlib is the only dependency of Bazel that comes from the host system, so let's
change that. There isn't much point in using the preinstalled version of a
single library while having everything else under third_party/ .
Change-Id: I60c129a41ff4a1b532f8b1d6e2508bd6e6b0a755
|
|
|
|
| |
Change-Id: Id34891c9abd4e254bad8b758347ecd3131bce4b2
|
|
|
|
|
|
| |
This is needed for gRPC.
Change-Id: I68c6b500d0e26742a25afef1754f5fcabf959ef0
|
|
|
|
| |
Change-Id: I9fac9d265ae9f1691be4dbb4b3bef6f35872b5ee
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit 5d737d642623: ("Some minor updates to the BUILD files.") made the
default visibility for the whole package public, and thus setting it
again in blaze_util target is rendundat.
While at it remove blaze_util_platform.h from srcs attribute of client
target, as it is already in hdrs list of blaze_util target and client
already depends on it, and thus it is not necessary to list it again
here.
--
Change-Id: I995c3cd6e2f63384acef4b24b9a082e7cb59331a
Reviewed-on: https://bazel-review.googlesource.com/#/c/3150/1
MOS_MIGRATED_REVID=119041634
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Check the return value of getcwd() and if it fails print
a message to the user and return -1.
This should fix the following warning:
third_party/ijar/zip_main.cc:175:32: warning: ignoring return value of
'char* getcwd(char*, size_t)', declared with attribute
warn_unused_result [-Wunused-result]
getcwd(output_root, PATH_MAX);
--
Change-Id: I8857e484f5baf60289d7c19a128f5a4616ae50e4
Reviewed-on: https://bazel-review.googlesource.com/#/c/3230/
MOS_MIGRATED_REVID=119029402
|
|
|
|
|
|
|
| |
--
Change-Id: Ib83af0d0a04dc6b173bef1df28d17abc7a3c824d
Reviewed-on: https://bazel-review.googlesource.com/#/c/3120/
MOS_MIGRATED_REVID=119027507
|
|
|
|
|
|
|
|
| |
Resources in `java_library`s get the external repo path added to them, e.g., `foo` becomes `external/git_remote_repo/foo`. It needs to be removed, though I'm not sure this is the right way to strip it ...
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1085
MOS_MIGRATED_REVID=119024770
|
|
|
|
|
|
|
| |
Then less special-casing is needed and these files are always read by the compiler anyway, so we don't lose any incrementality.
--
MOS_MIGRATED_REVID=119023956
|
|
|
|
|
|
|
|
|
| |
building watch OS 1 apps.
RELNOTES: Support apple_watch1_extension and apple_watch_extension_binary rules for creating watch OS 1 extensions.
--
MOS_MIGRATED_REVID=119000703
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118969066
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118967358
|
|
|
|
|
|
|
|
|
|
|
| |
android_binary (and java_binary).
RELNOTES[NEW]: The output of -printconfiguration of proguard is available
through an implicit "[target_name]_proguard.confg" output of android_binary (and
java_binary).
--
MOS_MIGRATED_REVID=118958246
|
|
|
|
|
|
|
| |
native rules to skylark rules and that returned from skylark rules to depending native rules. This fixes a bug where a skylark rule that did not touch the objc provider would automatically pass up the objc provider it received from dependencies to dependant native rules, leading to duplicate symbol linking errors when the same objc provider was exported twice.
--
MOS_MIGRATED_REVID=118947782
|
|
|
|
|
|
|
| |
names contain url, http or https.
--
MOS_MIGRATED_REVID=118946808
|
|
|
|
|
|
|
|
|
|
|
| |
In the experimental UI, use progress events as an occasion to
update the progress bar. However, to avoid unnecessary noise, only
do so, if the progress bar potentially changes with time.
--
Change-Id: I9bee093c29e0eb50e7fcce2fa6e941a02d615def
Reviewed-on: https://bazel-review.googlesource.com/#/c/3206
MOS_MIGRATED_REVID=118944208
|
|
|
|
|
|
|
|
|
| |
1) Introducing the action_config message in the crosstool protobuf definition. The only part of that definition that are implemented in this CL is the "tool" section, other parts will be implemented in future CLs. The proto fields are here now to avoid being delayed by release cycles at each step of the implementation.
2) Refactoring the implementation of the "feature algebra" that computes the enabled features for a given toolchain. An interface called "CrosstoolActivatable" is used to represent any participant int the feature algebra, and can be either a feature or an action_config.
--
MOS_MIGRATED_REVID=118943663
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118943054
|
|
|
|
|
|
|
|
|
| |
Fixed #1040
RELNOTES:none
--
MOS_MIGRATED_REVID=118941667
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118940625
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, the progress bar shows the 3 earliest started still running actions.
While this might give some indication about which actions delay the build process,
it lacks quantitative information about how long the delay is. By adding the current
run time to the progress bar, at least some quantitative information is provided.
--
Change-Id: Ib90eda67d87384a4372cda7779a09a44cea2b8dd
Reviewed-on: https://bazel-review.googlesource.com/#/c/3205
MOS_MIGRATED_REVID=118933973
|
|
|
|
|
|
|
|
|
|
| |
In this way, the ExperimentalStateTracker has access to all the information needed
to provide information about the run-time of currently running actions.
--
Change-Id: I0f4e48f39e9ebe63555e4bb1d70df2a6dbb65430
Reviewed-on: https://bazel-review.googlesource.com/#/c/3204
MOS_MIGRATED_REVID=118929758
|
|
|
|
|
|
|
|
|
|
|
| |
special-casing it in CppConfiguration.
This seems to be the most reasonable solution. I was toying with the idea of adding a field to CROSSTOOL but that would fail if you set libc_top to something other than what was specified in that file. If I had a infinite amount of time, I'd create a custom rule called cc_libc where libc_top would point so that this file can be referenced by an attribute, but since I don't, this seems to be workable compromise.
Also note that contrary to what you'd glean from the code, we don't actually have "compile" and "link" filegroups for libc.
--
MOS_MIGRATED_REVID=118921101
|
|
|
|
|
|
|
| |
Fixes #1087
--
MOS_MIGRATED_REVID=118919990
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118917025
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118819625
|
|
|
|
|
|
|
| |
for compatibility with JavaBuilder.
--
MOS_MIGRATED_REVID=118802288
|
|
|
|
|
|
|
|
|
| |
The compiler may implicitly load types that are direct dependencies but not
referred to in source, e.g. in the case of package-info files where the package
symbol is implicitly loaded to resolve annotations.
--
MOS_MIGRATED_REVID=118800795
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118786316
|
|
|
|
|
|
|
| |
BuildConfiguration.Fragment is much more complicated than it should be. Every little helps.
--
MOS_MIGRATED_REVID=118783105
|
|
|
|
|
|
|
|
|
| |
memory usage
Label instances do not share a single intern pool today, as some other objects, such as SkyKey and PackageIdentifier. This change allows all Label instantiations to use a single intern pool for better memory usage.
--
MOS_MIGRATED_REVID=118780952
|
|
|
|
|
|
|
|
|
| |
Noticed this while messing with remote runfiles.
RELNOTES: local_repository can take a relative path.
--
MOS_MIGRATED_REVID=118780775
|
|
|
|
|
|
|
|
|
| |
I was messing with filesystem dirtiness checkers and got an NPE, and I guess it
was so early in the build that the buildRequest didn't have WorkerOptions yet,
so I got a NPE from WorkerModule.buildComplete masking the actual NPE.
--
MOS_MIGRATED_REVID=118780059
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118775810
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/java/com/google/devtools/build/lib:analysis_test
This target is timeout flaky and internally we used 2 shard for
it, let do the same for the OSS test suite now we have the java
test launcher.
Fixes #1112.
--
MOS_MIGRATED_REVID=118768231
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixing a few issues with cc_configure that I encountered.
* The argument for rpath should be -Wl,-rpath.
* cc_configure should consider CPLUS_INCLUDE_PATH. I ran into this problem when using
a crosstool gcc which needs -I/usr/include.
* Check if -Wunused-but-set-parameter is available.
--
Change-Id: I73198b5b17674ecbf1b511e23fcc9331ca96c8e0
Reviewed-on: https://bazel-review.googlesource.com/#/c/3210/
MOS_MIGRATED_REVID=118763218
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118761993
|
|
|
|
|
|
|
|
|
| |
- Add milestones for the end of the year. 0.9 is a bit optimistic
- Add link from milestone version to the corresponding release
- Moved completed items to the correct milestones.
--
MOS_MIGRATED_REVID=118761783
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes the following warnings:
third_party/ijar/mapped_file_unix.cc:31:1: warning:
'MappedInputFileImpl' defined as a struct here but previously declared
as a class [-Wmismatched-tags]
struct MappedInputFileImpl {
^
./third_party/ijar/mapped_file.h:22:1: note: did you mean struct here?
class MappedInputFileImpl;
third_party/ijar/mapped_file_unix.cc:88:1: warning:
'MappedOutputFileImpl' defined as a struct here but previously declared
as a class [-Wmismatched-tags]
struct MappedOutputFileImpl {
^
./third_party/ijar/mapped_file.h:23:1: note: did you mean struct here?
class MappedOutputFileImpl;
--
Change-Id: Ie8269c0cfec41b4a1ddcdc9a9cd155ecac4b01d8
Reviewed-on: https://bazel-review.googlesource.com/#/c/3101
MOS_MIGRATED_REVID=118761176
|
|
|
|
|
|
| |
Actually, it's a bit more files than strictly necessary, but it's easier to maintain this way.
Change-Id: I22bba190940c1695f491cd28c7a7a95018d77bb1
|
|
|
|
|
|
|
| |
Also rename the build method from add* to set*.
--
MOS_MIGRATED_REVID=118746866
|
|
|
|
|
|
|
|
|
| |
instead of initializing all file objects to empty. Some annotation processors
speculatively open files and handle FileNotFoundException, and we were always
providing empty files.
--
MOS_MIGRATED_REVID=118730162
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118727286
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously turbine whitelisted -source and -target flags and ignored all other
configured javacopts, including custom annotation processor options and javac
debug flags.
The change switches to allowing all javacopts, and blackisting options that are
known to be incompatible.
Also ensure that invalid flags result in an error.
--
MOS_MIGRATED_REVID=118718745
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=118713377
|
|
|
|
|
|
|
| |
Fixes #855.
--
MOS_MIGRATED_REVID=118711400
|
|
|
|
|
|
|
|
| |
Also a bit of best practices (for issue #1081) that should be integrated
into the main documentation later when everything gets more stable.
--
MOS_MIGRATED_REVID=118706269
|
|
|
|
|
|
|
| |
is a no-op by default.
--
MOS_MIGRATED_REVID=118705742
|