| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
is a partial rollback of commit f1e257d because it turns out that loading sequentially can be a bottleneck.
--
MOS_MIGRATED_REVID=112628616
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If an aspect has specified its configuration fragment dependencies,
use these in place of the rule's.
Note that the dynamic configuration support for this is yet to come.
Also in this CL:
* RuleContext is constructed with a ruleClassNameForLogging, which allows
error messages involving aspects to be clearer.
RELNOTES[NEW]: Skylark aspects can now specify configuration fragment
dependencies with fragments and host_fragments like rules can.
--
MOS_MIGRATED_REVID=112614357
|
|
|
|
|
|
|
|
|
|
| |
environment variable DEVELOPER_DIR to commands.
If $(DEVELOPER_DIR) is included in the genrule command, we bootstrap the XCODE_VERSION_OVERRIDE environment variable to the command.
The contract with the actual action executor is, if XCODE_VERSION_OVERRIDE is present in the environment, to additionally bootstrap the DEVELOPER_DIR absolute path to the command.
--
MOS_MIGRATED_REVID=112605616
|
|
|
|
|
|
|
|
|
|
|
|
| |
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=112604261
|
|
|
|
|
|
|
|
|
| |
instead of just objc_binary.
RELNOTES:
--
MOS_MIGRATED_REVID=112601304
|
|
|
|
|
|
|
|
| |
javac's bespoke zip implementation is now off by default:
https://bugs.openjdk.java.net/browse/JDK-7018859
--
MOS_MIGRATED_REVID=112600878
|
|
|
|
|
|
|
| |
Instead of depending on //tools and //third_party in the base workspace.
--
MOS_MIGRATED_REVID=112599883
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112598805
|
|
|
|
|
|
|
| |
its intended use.
--
MOS_MIGRATED_REVID=112598772
|
|
|
|
|
|
|
|
|
|
| |
This is part of removing the requirement of having base_workspace in your
package_path for bazel builds.
This also removes --experimental_objc_gcov_binary, since it doesn't seem to be needed anymore.
--
MOS_MIGRATED_REVID=112595137
|
|
|
|
|
|
|
|
|
| |
Previously the crashing logger would allow the server process to survive
which could leave things in a weird state if a crash was expected. Instead
of throwing an exception shut down the runtime.
--
MOS_MIGRATED_REVID=112589751
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Updating the generate_workspace tool to:
- Respect dependency exclutions from the project object model (maven).
- Generate one rule per pom dependency or maven_jar source rule (using maven
group ID and artifact ID).
--
Change-Id: Ieb878f82be4352dcfb5755f8f71dfa7e592de78a
Reviewed-on: https://bazel-review.googlesource.com/#/c/2551/
MOS_MIGRATED_REVID=112574031
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112573386
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Baseline: e933d5e
+ 3d796fe: Rollback of commit
ac6ed79e1a3fa6b0ca91657b28e2a35f7e49758c.
+ 7a02e5d: Fix installer under OS X
+ 848740c: Fix bazel version for debian package
+ 7751d43: Add a method for getting the root of a rule workspace
to the Label method
Important changes:
- add loadfiles() query operator, to find skylark files loaded by
targets.
- Added ability to declare and use aspects in Skylark.
- Skylark load statements may now reference .bzl files via build
labels, in addition to paths. In particular, such labels can be
used to reference Skylark files in external repositories; e.g.,
load("@my_external_repo//some_pkg:some_file.bzl", ...).
Path-based loads are now deprecated and may be disabled in the
future. Caveats: Skylark files currently do not respect package
visibility; i.e., all Skylark files are effectively public. Also,
loads may not reference the special //external package.
- Relative paths can now be used for 'path' with
new_local_repository and local_repository.
|
|
|
|
|
|
|
| |
what kind of performance we could get from how we imagine it would work under Windows.
--
MOS_MIGRATED_REVID=112572621
|
|
|
|
|
|
|
| |
The generated project is not perfect, but this does unblock Manuel for the time being.
--
MOS_MIGRATED_REVID=112571724
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The help message of this option had the effect inversed. The default
--block_for_lock setting makes the client block waiting for the lock
when needed, and the flag needs to be unset with --noblock_for_lock
to instead exit immediately.
Also rename the dummy noblock_for_lock variable to blockForLock to match
the naming convention. The variable is not used anywhere, as this class
only exists for the help messages.
--
MOS_MIGRATED_REVID=112566287
|
|
|
|
|
|
|
|
|
| |
Fixes #676.
--
Change-Id: I7474d3e3071c99452b6e1835d6f70671f34b1fd9
Reviewed-on: https://bazel-review.googlesource.com/#/c/2693
MOS_MIGRATED_REVID=112564791
|
|
|
|
|
|
|
| |
Fixes #790
--
MOS_MIGRATED_REVID=112563137
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112562308
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112561390
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112555666
|
|
|
|
|
|
|
| |
These are unnecessary because Bazel now carries these tools with itself in the @bazel_tools repository.
--
MOS_MIGRATED_REVID=112555031
|
|
|
|
|
|
|
|
| |
The avoids misleading "Building libfoo.jar (0 files)" progress messages for
sourcejar-only compilations.
--
MOS_MIGRATED_REVID=112512879
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112507181
|
|
|
|
|
|
|
| |
all so that custom implementations can have custom options passed around.
--
MOS_MIGRATED_REVID=112502778
|
|
|
|
|
|
|
|
|
|
|
| |
Also, don't require the :stl attribute to be defined by all rules that
use CcLibraryHelper.
This makes it possible for other languages to use CcLibraryHelper to
create a CppCompilationContext.
--
MOS_MIGRATED_REVID=112494452
|
|
|
|
|
|
|
|
| |
This is in preparation for removing the requirement that base_workspace be in
bazel's package_path.
--
MOS_MIGRATED_REVID=112489640
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112478681
|
|
|
|
|
|
|
|
| |
This is in preparation for removing the requirement that base_workspace be in
bazel's package_path.
--
MOS_MIGRATED_REVID=112477785
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This executable in the workspace can be another Bazel binary whose
version will change with the code it's next to, or a shell script which
downloads a fixed version from some location.
RELNOTES: A tools/bazel script in the workspace will be executed
as an opportunity to use a fixed version of Bazel (not implemented for
the homebrew recipe yet).
Fixes #521
--
Change-Id: Id06177d9c2b259cd9d6fd62edb5abe541342dd05
Reviewed-on: https://bazel-review.googlesource.com/2620
MOS_MIGRATED_REVID=112477232
|
|
|
|
|
|
|
| |
Fixes #730.
--
MOS_MIGRATED_REVID=112475309
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112474631
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Refactored IntelliJSkylarkAspectTest. Eventually that test will be
merged with AndroidStudioInfoAspect test to validate implementation
equivalence.
2. Exposed ``root`` and ``is_source`` on Artifacts to Skylark.
3. Skylark aspect implementation outputs sources and dependencies
information.
--
MOS_MIGRATED_REVID=112473407
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112472854
|
|
|
|
|
|
|
| |
arguments (seems too messy for a family of functions).
--
MOS_MIGRATED_REVID=112472644
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112466264
|
|
|
|
|
|
|
|
|
|
|
| |
It is counter-intuitive to read ConnectToServer(false). By having
/*start=*/ in front of the boolean parameter the intention gets clear
(i.e., if it should or not start the Java server).
--
Change-Id: I74847deb6ec7daba62facd7a746d418943448182
Reviewed-on: https://bazel-review.googlesource.com/#/c/2680
MOS_MIGRATED_REVID=112466249
|
|
|
|
|
|
|
| |
The current set-up was overwriting the XML_OUTPUT_FILE of unittest_test, leading to weird error on ci.bazel.io.
--
MOS_MIGRATED_REVID=112462362
|
|
|
|
|
|
|
| |
It is currently unused and messes up IDEs because it requires a few dependencies that are not in the source tree (most notably, jimfs)
--
MOS_MIGRATED_REVID=112461226
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While BuildViewTestCase now has an update() function, it also has a lot of
legacy cruft that doesn't match how the code is used in production. This also
makes the test code a bit simpler.
Also add a couple missing fail() statements.
This is in preparation for adding a couple more tests; we don't have good
test coverage for interaction between Skylark aspects and native rules and
vice versa, especially for error scenarios.
I may reuse some of the AspectTest code, but that inherits AnalysisTestCase.
Inheriting AnalysisTestCase here also makes that easier.
--
MOS_MIGRATED_REVID=112460142
|
|
|
|
|
|
|
|
|
| |
Somewhat. The generated IntelliJ project is still somewhat broken and you need to manually exclude a few directories to use it and there is a mystical error about a missing method on truth.MapSubject, but at least now it fails in a less spectacular way.
Fixes #796.
--
MOS_MIGRATED_REVID=112458948
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- update some comments
- add some comments to make it easier to follow
- delete some dead code, in particular the SkyframeDependencyResolver can
never be null; remove an non-applicable @Nullable annotation
I'm trying to figure out how the error handling code works, in order to add
support for interleaved loading+analysis, which requires handling loading
errors in this code path.
--
MOS_MIGRATED_REVID=112456674
|
|
|
|
|
|
|
| |
This will create a non-dummy XML file for all our java_test.
--
MOS_MIGRATED_REVID=112449480
|
|
|
|
|
|
|
|
|
| |
This make those test target compatible with --nolegacy_bazel_java_test.
--
Change-Id: I2316c9aa53327b417ecce5fd5dab95ec726da11d
Reviewed-on: https://bazel-review.googlesource.com/#/c/2690
MOS_MIGRATED_REVID=112446514
|
|
|
|
|
|
|
|
| |
Because `appengine_war` is not defined by default, `bazel build` fails unless loading. It would be nice to add the code to load the rule in the tutorial.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/794
MOS_MIGRATED_REVID=112415835
|
|
|
|
| |
Change-Id: I99487b78a4f9a564c0618209f638425e2e39baa6
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112409554
|
|
|
|
|
|
|
|
|
|
|
| |
With latest change to the bootstrap compilation, some options
were wrongly moved around.
Tested with `source scripts/ci/build.sh; bazel_build` for JAVA_VERSION
1.7 and 1.8.
--
MOS_MIGRATED_REVID=112409496
|
|
|
|
|
|
|
|
|
|
| |
This method was used only twice. Now there is only one entry point for requesting
a rule in the external package (RepositoryFunction#getRule(String, Environment)).
This is a step towards supporting loading skylark rules in the workspace file from
remote repository.
--
MOS_MIGRATED_REVID=112407797
|