| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
Declare openjdk-9-jdk as Conflicts
Progress towards #1456
--
Change-Id: I67c17b78f90f81dbcc9c39bf6f3915789662fa94
Reviewed-on: https://bazel-review.googlesource.com/#/c/3951
MOS_MIGRATED_REVID=126402113
|
|
|
|
| |
Change-Id: Iaa7f2263aa2a2d8792618ff564e1eee818b5b982
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126391895
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the progress bar cannot be updated in place, every additional writing
of the progress bar clutters up the log. Of course, this could be controlled
by adding --show_progress_rate_limit or even --noshow_progress options to the
invocation; however, it turns out that users expect a bazel to just automatically
reduce its output rate. Therefore, specify a minimal value for the progress rate
limit of 2 seconds if the progress bar cannot be updated in place. Also, increase
the time rate for purely time-based updates to 20s in this case.
Moreover, only automatically redraw the progress bar after an INFO/WARNING/... message,
if it can be updated in place.
--
Change-Id: I7d06aa04acec457ec0a5d20ac32ede4cf80f7170
Reviewed-on: https://bazel-review.googlesource.com/#/c/3944
MOS_MIGRATED_REVID=126387987
|
|
|
|
|
|
|
|
|
| |
We have the source so build from sources instead. This was
causing strange behavior were the input file was conflicting
with the output file of the corresponding java_library but
was matched by the glob.
Change-Id: Ie0b70215d1862627747bd7b83f075743c904c967
|
|
|
|
|
|
| |
We don't use them and one of the test file contains a space that we don't support in label.
Change-Id: I4752860788bd20455ba659a89586e66e2896863d
|
|
|
|
|
|
| |
Also correctly cite this dependency in the README file
Change-Id: I2bca5102b3c7871a2f6a735103273bc25f853c9d
|
|
|
|
|
|
|
| |
Android split transitions.
--
MOS_MIGRATED_REVID=126378169
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126375064
|
|
|
|
|
|
|
|
|
|
|
|
| |
This warning is printed on every invocation, and the visual noise helps blind
the user to other more imporant warnings. Presumably they have chosen to set
--jobs high for a reason. Help them make a good choice with the documentation,
then don't distract them further.
RELNOTES: Remove warning for high value of --jobs.
--
MOS_MIGRATED_REVID=126369509
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126354275
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126344189
|
|
|
|
|
|
|
|
|
|
|
| |
blaze handling.
- Converted to correct upstreamed options
- Handling of bitcode when creating dynamic libraries
- New LTOBackendAction derived from SpawnAction that discovers and adds the imported bitcode files identified by the LTO indexing step.
--
MOS_MIGRATED_REVID=126344132
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126333303
|
|
|
|
|
|
|
|
| |
(2) Refactor the simple query concurrency support by introducing QueryExpression#canEvalConcurrently and removing the primitive BinaryOperatorExpression#evalConcurrently and the hardcoded SkyQueryEnvironment logic around it. This way each QueryExpression can safely manage its own concurrency. A followup CL will ensure that concurrent evaluation occurs for as much of the query expression as possible, rather than just for the top-level query expression node.
(3) Make a few query internals public.
--
MOS_MIGRATED_REVID=126324637
|
|
|
|
|
|
|
| |
* Add in some line breaks for easier to read output.
--
MOS_MIGRATED_REVID=126315204
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126310706
|
|
|
|
|
|
|
|
|
|
|
| |
As we also collect design documents on unimplemented designs,
it is important to keep status information with our design
documents.
--
Change-Id: I3e08a8b05daf7a0c7f12cffbe4a8e350de5e34f8
Reviewed-on: https://bazel-review.googlesource.com/#/c/3943
MOS_MIGRATED_REVID=126307804
|
|
|
|
|
|
|
| |
sane Java API for now)
--
MOS_MIGRATED_REVID=126306559
|
|
|
|
|
|
|
| |
--
Change-Id: I53ec66581c59d4bba8460fb3e5d20258ea36d0f1
Reviewed-on: https://bazel-review.googlesource.com/#/c/3940
MOS_MIGRATED_REVID=126306276
|
|
|
|
|
|
|
|
|
| |
is necessary for <style parent="">.
The previous code omitted empty strings to avoid the <attr format=""> case which is an error for aapt.
--
MOS_MIGRATED_REVID=126305040
|
|
|
|
|
|
|
|
| |
These don't do anything for a 64-bit JVM.
Also remove some very old GC tuning flags for --batch.
--
MOS_MIGRATED_REVID=126303269
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add .dll as a shared library type like .so
If we have target:
cc_binary(
name = "bar.dll",
srcs = ["bar.cc"],
linkshared = 1,
)
Now we can build a dll using bazel build //foo:bar.dll
If the target name is still bar.so, the wrapper script also
build the dll by copying the output file to bar.dll.
--
Change-Id: Ie3d1fb83965ddf691d0cc4734a61a0b0ce89d948
Reviewed-on: https://bazel-review.googlesource.com/#/c/3931
MOS_MIGRATED_REVID=126301390
|
|
|
|
|
|
|
|
|
|
| |
We already have some design documents committed to our documentation
pages. Add an index of those, under the 'Contribute!' section.
--
Change-Id: I9331f13d9f145668991f26dd301c10b4a7f06216
Reviewed-on: https://bazel-review.googlesource.com/#/c/3942
MOS_MIGRATED_REVID=126300855
|
|
|
|
|
|
|
|
|
|
|
| |
run following commands to test it:
bazel build --cpu=x64_windows_msvc examples/windows/dll:hello
./bazel-bin/examples/windows/dll/hello
--
Change-Id: I096f6ff66473b1c9980b0aa36ec291f39512dd71
Reviewed-on: https://bazel-review.googlesource.com/#/c/3932
MOS_MIGRATED_REVID=126300284
|
|
|
|
|
|
|
| |
This way it won't print if the repo maintainer doesn't set the repo name.
--
MOS_MIGRATED_REVID=126300205
|
|
|
|
|
|
|
|
|
|
|
|
| |
This stops Bazel from passing some of the gcc options to wrapper script.
Options we get rid of:
-c -o -MD -MF -frandom-seed -isystem -iquote -I
--
Change-Id: I416b393c6875a2033d5382a644471c416cd5e8d1
Reviewed-on: https://bazel-review.googlesource.com/#/c/3930
MOS_MIGRATED_REVID=126299789
|
|
|
|
|
|
|
| |
attributes as their parameters (instead of using an attribute map).
--
MOS_MIGRATED_REVID=126298988
|
|
|
|
|
|
|
|
|
| |
Also add missing dependencie on the javacutil tooling.
--
Change-Id: Idba4ddc2e79da4916925327e2f15337e86658a5d
Reviewed-on: https://bazel-review.googlesource.com/#/c/3915
MOS_MIGRATED_REVID=126298979
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126298962
|
|
|
|
|
|
|
| |
--
Change-Id: I5d420298aa841d04059462c10acb263ecf5cec28
Reviewed-on: https://bazel-review.googlesource.com/#/c/3941
MOS_MIGRATED_REVID=126296592
|
|
|
|
|
|
|
| |
Usages have since been removed.
--
MOS_MIGRATED_REVID=126296555
|
|
|
|
|
|
|
|
|
|
|
| |
Also, the number of pending items seems to 'leak' and always increase.
Be sure to add each package only once, even if the computation has to be restarted.
RELNOTES: The progress message would not clear packages that need to be loaded twice.
--
MOS_MIGRATED_REVID=126295556
|
|
|
|
|
|
|
|
|
| |
that's what it does.
In particular, it affects Windows.
--
MOS_MIGRATED_REVID=126293339
|
|
|
|
|
|
|
|
|
|
|
| |
If this is set to true (which it is by default), JavaCompilationHelper will set the "supports-workers" tag on the execution info for the Javac SpawnAction. If it is explicitly set to false, this tag will be absent.
In a follow-up CL, the WorkerSpawnStrategy will check whether this tag is present and fallback to non-worker execution if not.
This is needed to safely enable workers by default in Bazel without breaking the older JDK7 JavaBuilder, which does not support workers yet.
--
MOS_MIGRATED_REVID=126290991
|
|
|
|
|
|
|
|
| |
This needs to predate the rest of the changes to the checker framework to keep the build green.
Also add the source of javacutil part of the checker framework, that will be included in the next change.
Change-Id: Ie18d0e8e21035ce5141416e552a83d893f71b88b
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The ExperimentalEventHandler uses no functionality of BlazeCommandEventHandler,
hence there really is no need whatsoever for ExperimentalEventHandler to be
a subclass of BlazeCommandEventHandler. So, remove this inheritance to clean
up our class hierarchy; instead let the ExperimentalEventHandler just implement
the EventHandler interface.
--
Change-Id: I504f727190a12882dd8b7c37811a821e3ba50400
Reviewed-on: https://bazel-review.googlesource.com/#/c/3926
MOS_MIGRATED_REVID=126282974
|
|
|
|
|
|
|
| |
The first option was renamed to --java_deps, and the second was a no-op.
--
MOS_MIGRATED_REVID=126280008
|
|
|
|
|
|
|
|
|
| |
"supports-workers" execution info tag.
This is a new requirement which helps Blaze decide whether an action can be executed via workers or not.
--
MOS_MIGRATED_REVID=126279864
|
|
|
|
|
|
|
| |
every process wrapper again.
--
MOS_MIGRATED_REVID=126279021
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126275468
|
|
|
|
|
|
|
| |
Previously, the command-line reference page put a line break between them.
--
MOS_MIGRATED_REVID=126274327
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
legacy_native_support makes it so that Bazel copies .so's instead of linking.
This allows Bazel to include third-party native code without running an NDK.
Turning it off allows Bazel to actually compile native code, but at the cost
of this copy case no longer working without an NDK, and creating an unnecessary
shared library which will most likely never be used.
This CL makes it so that if no actual source code or static libraries are
in the transitive closure, the linker is not run at the android_binary level.
This means that legacy_native_support as a separate concept can be removed,
and it is - the attribute remains, but is a no-op. This will be removed in
a future change. The matching flag (--legacy_android_native_support) has
already been removed.
RELNOTES: The link mode for Android native code is now automatically determined
based on the transitive closure of cc_libraries, and legacy_native_support is
now a no-op. --legacy_android_native_support has been removed.
--
MOS_MIGRATED_REVID=126244755
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126235788
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126215213
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke builds that use apple_genrule.
*** Original change description ***
Move platform environment from xcrun_action to apple_action.
This change ensures that scripts that don't need to be wrapped with
xcrun_action (like actoolwrapper, ibtoolwrapper, and friends, because
they internally invoke xcrunwrapper) also have the Xcode version and
platform envvars set.
RELNOTES:
--
MOS_MIGRATED_REVID=126205606
|
|
|
|
|
|
|
| |
experimental_objc_library.
--
MOS_MIGRATED_REVID=126204758
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126200568
|
|
|
|
|
|
|
| |
this and commit 116c2f6724718fc408e0c73c9026d89281c75e87 using Guava's Ascii#truncate.
--
MOS_MIGRATED_REVID=126198762
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new "define" method replaces the now deprecated writeToValuesXml method. This provides three benefits:
* An agnostic writing interface to the XmlResourceValue classes, easing the replacement of them with a proper xml writer.
* A delayed write which allows the StyleableXmlResourceValue to claim AttrXmlResourceValue definitions before writing.
* Centralized method of source attribution, enabling a less verbose way to indicate multiple values came from a single xml source file.
An example of the new interface writing the StyleXmlResourceValue:
ValuesResourceDefinition definition = mergedDataWriter
.define(key)
.derivedFrom(source)
.startTag("style")
.named(key)
.optional()
.attribute("parent")
.setTo(parent)
.closeTag();
for (Entry<String, String> entry : values.entrySet()) {
definition = definition
.startItemTag()
.named(entry.getKey())
.close()
.addCharactersOf(entry.getValue())
.endTag();
}
definition.endTag().save();
--
MOS_MIGRATED_REVID=126196028
|