aboutsummaryrefslogtreecommitdiffhomepage
path: root/src
Commit message (Collapse)AuthorAge
* Implement an abstraction layer over java.lang.Process so that the Windows ↵Gravatar Lukacs Berki2016-07-04
| | | | | | | implementation can eventually be plugged in. -- MOS_MIGRATED_REVID=126404913
* Add all the sources to //:srcs filegroup and add a check to detectGravatar Damien Martin-Guillerez2016-07-01
| | | | | | | | | | | missing file to it. We need to activate this check on presubmits -- Change-Id: Ia95e92d3816ce92bb69bc0e2cf56e9c60b68d970 Reviewed-on: https://bazel-review.googlesource.com/#/c/3949/ MOS_MIGRATED_REVID=126404792
* experimental UI: enforce a minimal progress rate limiting if curses unavailableGravatar Klaus Aehlig2016-07-01
| | | | | | | | | | | | | | | | | | 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
* RELNOTES: Use the correct build configuration for shared native deps during ↵Gravatar Googler2016-07-01
| | | | | | | Android split transitions. -- MOS_MIGRATED_REVID=126378169
* Whilelist blog.llvm.org and add ThinLTO reference to bazelGravatar Googler2016-07-01
| | | | | -- MOS_MIGRATED_REVID=126375064
* bazel: move the "--jobs too high" warning to documentation.Gravatar Googler2016-07-01
| | | | | | | | | | | | 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
* C++ reimplementation of singlejar tool: first checkin.Gravatar Sasha Smundak2016-07-01
| | | | | -- MOS_MIGRATED_REVID=126354275
* Batch prefetch now also retrieves the deps from the node's previous run.Gravatar Eric Fellheimer2016-07-01
| | | | | -- MOS_MIGRATED_REVID=126344189
* ThinLTO changes for upstreamed compiler implementation and other fixes to ↵Gravatar Googler2016-07-01
| | | | | | | | | | | 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
* Ignore make variables undefined for requested platform.Gravatar Dmitry Lomov2016-07-01
| | | | | -- MOS_MIGRATED_REVID=126333303
* (1) Allow QueryExpressionMapper#map to throw a QueryException.Gravatar Nathan Harmata2016-07-01
| | | | | | | | (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
* * Clean up of the old Iterable<String> method of writing xmlGravatar Googler2016-07-01
| | | | | | | * Add in some line breaks for easier to read output. -- MOS_MIGRATED_REVID=126315204
* Make java_classpath flag non-experimentalGravatar Liam Miller-Cushon2016-07-01
| | | | | -- MOS_MIGRATED_REVID=126310706
* Add native process management for Windows and its Java bindings (without a ↵Gravatar Lukacs Berki2016-07-01
| | | | | | | sane Java API for now) -- MOS_MIGRATED_REVID=126306559
* Fixes the case where an optional attribute needs to be an empty string. This ↵Gravatar Googler2016-07-01
| | | | | | | | | 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
* Stop passing -client and -server to the JVM.Gravatar Googler2016-07-01
| | | | | | | | These don't do anything for a 64-bit JVM. Also remove some very old GC tuning flags for --batch. -- MOS_MIGRATED_REVID=126303269
* Make building dll less a hack on WindowsGravatar Yun Peng2016-07-01
| | | | | | | | | | | | | | | | | | | | 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
* Make repository name warning less noisyGravatar Kristina Chodorow2016-07-01
| | | | | | | This way it won't print if the repo maintainer doesn't set the repo name. -- MOS_MIGRATED_REVID=126300205
* Skylark documentation update: callback functions have to list the required ↵Gravatar Florian Weikert2016-07-01
| | | | | | | attributes as their parameters (instead of using an attribute map). -- MOS_MIGRATED_REVID=126298988
* Remove some android tool paths from test/shell/bazel/testenv.sh.bazelGravatar Googler2016-07-01
| | | | | | | Usages have since been removed. -- MOS_MIGRATED_REVID=126296555
* The message "currently loading: " is often stuck on the first loaded package. Gravatar Googler2016-07-01
| | | | | | | | | | | 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
* Rename the property io.bazel.UnixFileSystem to io.bazel.EnableJni because ↵Gravatar Lukacs Berki2016-07-01
| | | | | | | | | that's what it does. In particular, it affects Windows. -- MOS_MIGRATED_REVID=126293339
* Add a javac_supports_workers attribute to the java_toolchain rule.Gravatar Philipp Wollermann2016-07-01
| | | | | | | | | | | 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
* ExperimentalEventHandler: remove unnecessary inheritanceGravatar Klaus Aehlig2016-06-30
| | | | | | | | | | | | | 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
* Remove --experimental_java_deps and --experimental_incremental_ijars.Gravatar Ulf Adams2016-06-30
| | | | | | | The first option was renamed to --java_deps, and the second was a no-op. -- MOS_MIGRATED_REVID=126280008
* Fix existing usages of persistent workers to include the new ↵Gravatar Philipp Wollermann2016-06-30
| | | | | | | | | "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
* Do redirection of stdout / stderr in Java instead of reimplementing it in ↵Gravatar Philipp Wollermann2016-06-30
| | | | | | | every process wrapper again. -- MOS_MIGRATED_REVID=126279021
* Add help text for the --invocation_policy option of canonicalize-flags.Gravatar Ulf Adams2016-06-30
| | | | | -- MOS_MIGRATED_REVID=126275468
* Change expansion for help --long/short to render more nicely.Gravatar Ulf Adams2016-06-30
| | | | | | | Previously, the command-line reference page put a line break between them. -- MOS_MIGRATED_REVID=126274327
* Support copy-only native code in modern native support for android_binary.Gravatar Michael Staib2016-06-30
| | | | | | | | | | | | | | | | | | | | | | | 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
* Add compilation mode handling to swift_library.Gravatar Dmitry Shevchenko2016-06-30
| | | | | -- MOS_MIGRATED_REVID=126235788
* Make header compilation flag non-experimentalGravatar Liam Miller-Cushon2016-06-30
| | | | | -- MOS_MIGRATED_REVID=126215213
* Add platform-specific common compile and link flags toGravatar Cal Peyser2016-06-30
| | | | | | | experimental_objc_library. -- MOS_MIGRATED_REVID=126204758
* Switches XmlResourceValue writing to the "define" api.Gravatar Googler2016-06-30
| | | | | -- MOS_MIGRATED_REVID=126200568
* Cap depserver log lines of blaze stderr lines at 1000 chars. Implement both ↵Gravatar Nathan Harmata2016-06-30
| | | | | | | this and commit 116c2f6724718fc408e0c73c9026d89281c75e87 using Guava's Ascii#truncate. -- MOS_MIGRATED_REVID=126198762
* Creates a fluent api that moves the xml generation into the data writer.Gravatar Googler2016-06-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Fix Windows detection in unittest.bash.Gravatar Dmitry Lomov2016-06-29
| | | | | | | -- Change-Id: Iedc81e6502b374f5188e54d02b396502038f5174 Reviewed-on: https://bazel-review.googlesource.com/#/c/3924/ MOS_MIGRATED_REVID=126194925
* Fix/work around bad interaction between interface deps and LIPO. Previously ↵Gravatar Googler2016-06-29
| | | | | | | looking at the declared include srcs of all transitive deps was sufficient as these contained all headers possibly relevant even with LIPO optimizations. With interface deps, we cut off dependencies (and thus headers) that aren't directly includable. To still make those available to LIPO, we need to also supply the declared include sources coming from lipo scannables. -- MOS_MIGRATED_REVID=126183112
* Make experimental UI resistent to late-reported eventsGravatar Klaus Aehlig2016-06-29
| | | | | | | | | | | | | Sometimes the event reporting the completion of the last action can, effectively, overtake the event reporting the completion of last action. To avoid late writing to the output stream don't start the update thread after the completion of the build is reported. There is nothing to update then any more anyway. -- Change-Id: Ibbb6d025635a9daa233c2b28ca64a1ae4896ce47 Reviewed-on: https://bazel-review.googlesource.com/#/c/3922 MOS_MIGRATED_REVID=126182576
* Make Windows bootstrapping work again by temporarily disabling JNI.Gravatar Lukacs Berki2016-06-29
| | | | | -- MOS_MIGRATED_REVID=126177747
* experimental UI: on failing tests, don't state "completed sucessfully"Gravatar Klaus Aehlig2016-06-29
| | | | | | | | | | | | | | Currently, if a build completes with tests failing, the final status message is "INFO: Build completed successfully, xxx actions". While technically correct, it might mislead the user to believing all tests have passed (especially when only looking at the status in the terminal title). Therefore, if a build completes with failing tests, mention the number of failed tests in the final status message. -- Change-Id: I9234fbfdf2ad43dd29af660966dde73bf0c9311a Reviewed-on: https://bazel-review.googlesource.com/#/c/3918 MOS_MIGRATED_REVID=126176452
* GPLv2 + Classpath exception compliance: ship the source code of jformatstringGravatar Damien Martin-Guillerez2016-06-29
| | | | | | | | | | | Technically, jformatstring has no problem because we were shiping the source of in the jar file itself but that's easier to keep track of it if we actually vendor the source and build from the source. -- Change-Id: I80fc47ddeafc60263db47f33bfa9a2f2d7e2188d Reviewed-on: https://bazel-review.googlesource.com/#/c/3914 MOS_MIGRATED_REVID=126174813
* Refactor how coverage support files get to test actions.Gravatar Lukacs Berki2016-06-29
| | | | | | | | | Previously we used labels in each configuration fragment that then got added to every test action. Instead, we now have a filegroup under //tools/test for coverage files that truly need to be on the inputs of every test action and collect language-specific support files in InstrumentedFilesProvider. This makes configuration creation simpler and makes it possible to turn --crosstool_top into something else other than a filegroup (previously, it was that filegroup that got added to every test action) -- MOS_MIGRATED_REVID=126170241
* experimental UI: honor --show_timestampsGravatar Klaus Aehlig2016-06-29
| | | | | | | | | | | In the experimental UI, also support the --show_timestamps option which asks that for each event a timestamp be added to the the output. Fixes #1436. -- Change-Id: I8f9db958525edfbca12ed2c1f1396f25f865b897 Reviewed-on: https://bazel-review.googlesource.com/#/c/3916 MOS_MIGRATED_REVID=126165328
* For --aspects parameter, ignore top-level targets that are not rules.Gravatar Dmitry Lomov2016-06-29
| | | | | -- MOS_MIGRATED_REVID=126161513
* Add java_plugin.generates_apiGravatar Liam Miller-Cushon2016-06-29
| | | | | | | | | | | | | | This attribute marks annotation processors that generate API code. If a rule uses an API-generating annotation processor, other rules depending on it can refer to the generated code only if their compilation actions are scheduled after the generating rule. In the future, annotation processors will only be considered by header compilation if they set generates_api=1. -- MOS_MIGRATED_REVID=126152384
* Minor documentation and visibility tweaks to InMemoryNodeEntry and ↵Gravatar Janak Ramakrishnan2016-06-29
| | | | | | | InvalidatedNodeEntry. -- MOS_MIGRATED_REVID=126139179
* Record whether the attr is defined or referenced in the styleable. Despite ↵Gravatar Googler2016-06-29
| | | | | | | the functional equality, the definition type of the attribute has direct impact on the order in which the attribute appears in the styleable array. -- MOS_MIGRATED_REVID=126126122
* Canonicalize some TransitiveTraversalValue objects -- those corresponding to ↵Gravatar Janak Ramakrishnan2016-06-29
| | | | | | | | | error-free built-in rules, and to non-rules. This should save memory, as well as CPU for built-in rules, since we don't have to make sets out of their providers more than once. Also fix a bug in the equality check where we weren't comparing the canHaveAnyProvider field properly. -- MOS_MIGRATED_REVID=126121351
* Collect logic related to extra Proguard outputs in one place.Gravatar Googler2016-06-29
| | | | | -- MOS_MIGRATED_REVID=126120891
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-06 05:05:23 +0000