| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
declare required configuration fragments: from
*everything* to *nothing*.
Now that all builtin rules properly declare their fragments,
the "backwards compatibility" concern that inspired the
original behavior is no longer needed.
This impacts, for example, filegroup rules, which have
nothing to declare.
--
MOS_MIGRATED_REVID=106433791
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/524
MOS_MIGRATED_REVID=106431355
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106418732
|
|
|
|
|
|
|
| |
RELNOTES: Bazel does strict validation of include files now to ensure correct incremental builds. If you see compilation errors when building C++ code, please make sure that you explicitly declare all header files in the srcs or hdrs attribute of your cc_* targets and that your cc_* targets have correct "deps" on cc_library's that they use.
--
MOS_MIGRATED_REVID=106410969
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106410161
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106409855
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106407898
|
|
|
|
|
|
|
|
|
|
| |
philwo@philwo:/tmp/bazel$ ./output/bazel query 'labels(srcs, @androidndk//:arm-linux-androideabi-4.9-v7a-gnu-libstdcpp-toolchain_files)'
INFO: Empty results
This caused compiliation failures when building //examples/android/java/bazel:hello_world with sandboxing enabled.
--
MOS_MIGRATED_REVID=106405986
|
|
|
|
|
|
|
|
|
|
|
|
| |
//examples/android/java/bazel:hello_world with sandboxing enabled.
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot open crtbegin_so.o: No such file or directory
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot open crtend_so.o: No such file or directory
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lc
external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot find -ldl
--
MOS_MIGRATED_REVID=106405880
|
|
|
|
|
|
|
| |
aar does not contain the transitive closure of the target, as this is a common misconception.
--
MOS_MIGRATED_REVID=106396742
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106389517
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106382513
|
|
|
|
|
|
|
|
|
| |
Constants.ANDROID_DEP_PREFIX.
This regrettably entails adding the options parser to the embedded tools in the Bazel binary, but that's only a temporary measure until the embedded binaries are compiled (and not provided in source from)
--
MOS_MIGRATED_REVID=106379028
|
|
|
|
|
|
|
| |
($python_precompile, etc.)
--
MOS_MIGRATED_REVID=106352835
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106333445
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106329484
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106327492
|
|
|
|
|
|
|
|
|
| |
Adds documentation about the associated manifest processing to add a compatible-screens section.
RELNOTES: 420 dpi is now a valid density for andoid_binary.densities.
--
MOS_MIGRATED_REVID=106324044
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106323413
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106315882
|
|
|
|
|
|
|
|
|
| |
sense.
RELNOTES: The names of the clang compilers in the Android NDK crosstool no longer reference gcc.
--
MOS_MIGRATED_REVID=106305253
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106302500
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106300290
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106299058
|
|
|
|
|
|
|
|
|
| |
LocalGccStrategy / LocalLinkStrategy with SpawnGccStrategy / SpawnLinkStrategy.
RELNOTES: C++ compile actions run in a sandbox now on systems that support sandboxed execution.
--
MOS_MIGRATED_REVID=106299043
|
|
|
|
|
|
|
| |
validating includes and updating action inputs is clearly separated and easier to understand now.
--
MOS_MIGRATED_REVID=106298050
|
|
|
|
|
|
|
| |
Tested by running "bazel query @bazel-j2objc//...' in an empty workspace.
--
MOS_MIGRATED_REVID=106292152
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106291132
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106287576
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106182161
|
|
|
|
|
|
|
| |
maximum size, based off a reasonably larged sized benchmark.
--
MOS_MIGRATED_REVID=106180595
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106174495
|
|
|
|
|
|
|
|
|
|
| |
Simplifies the runtime graph when TransitiveTraversalFunction is used.
Also moves an error reporting method from the base function to the
TransitiveTargetFunction, which is the only one that uses it.
--
MOS_MIGRATED_REVID=106109745
|
|
|
|
|
|
|
| |
for the generated Android NDK crosstool so that compilation works when sandboxed.
--
MOS_MIGRATED_REVID=106092381
|
|
|
|
|
|
|
| |
PackageIdentifier, where it actually belongs.
--
MOS_MIGRATED_REVID=106086272
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fragments map into the BuildConfiguration constructor.
This guarantees that other access points into the constructor (e.g.
BuildConfigurationFunction for dynamic configs) apply the same ordering.
BuildConfiguration needs its fragments stored in a consistent
order to, e.g., make sure buildMnemonic() produces
consistent results.
--
MOS_MIGRATED_REVID=106079920
|
|
|
|
|
|
|
| |
It's always null
--
MOS_MIGRATED_REVID=106053287
|
|
|
|
|
|
|
| |
to a remote repository.
--
MOS_MIGRATED_REVID=106051348
|
|
|
|
|
|
|
|
| |
Also remove a bunch of custom uses of EventCollector, and use the (already
existing) EventCollectionApparatus instead.
--
MOS_MIGRATED_REVID=106047665
|
|
|
|
|
|
|
| |
--
Change-Id: Ic19a8292e1c57623085daa6ce3cbf280cdf7129e
Reviewed-on: https://bazel-review.googlesource.com/2180
MOS_MIGRATED_REVID=106035838
|
|
|
|
|
|
|
| |
This makes it possible to call these methods with lists from Skylark, which are internally Iterable<>'s but not Collection<>'s.
--
MOS_MIGRATED_REVID=106003065
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105999401
|
|
|
|
|
|
|
|
|
| |
order. In general, there's no advantage in Blaze to FIFO, and it means that we effectively do breadth-first graph traversal. When we must hold state for incomplete nodes (as we do with action execution, or more generally, as we do in Skyframe), this increases our memory footprint.
LIFO is not exactly depth-first traversal, since we are multithreaded, but to a first approximation, it looks like a depth-first traversal with "width" the number of threads (at each level of the graph, #(threads) nodes are visited).
--
MOS_MIGRATED_REVID=105995014
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105994907
|
|
|
|
|
|
|
| |
For native aspects, AspectClass is a facade for Class<AspectFactory<...>>.
--
MOS_MIGRATED_REVID=105986390
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In SkyQueryEnvironment, the buildTransitiveClosure method ignored the
error messages in successfully evaluated TransitiveTraversalValues,
under the belief that any such error messages are also obtainable by
calling getMissingAndExceptions. This happens to be true right now,
but may not be true in the future.
If, in particular, the TransitiveTraversal skyfunction inlines its
call to the TargetMarker skyfunction, those error messages won't be
available through getMissingAndExceptions.
--
MOS_MIGRATED_REVID=105980430
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, a TransitiveTraversalFunction computed a value that
contained an exception only if the exception resulted from a failure
to load the function's immediate target. If the target had transitive
dependencies on other targets, those other targets would be loaded, but
any errors resulting from loading those targets would not be retained.
SkyQueryEnvironment impromperly used a SkyFrame mechanism (which was
solely intended to ensure equivalent semantics between keep-going and
no-keep-going evaluations) to discover errors in the set of transitive
children of TransitiveTraversal nodes.
In order to transition SkyQueryEnvironment away from that mechanism,
this CL changes TransitiveTraversalFunction to remember the first error
message encountered while loading its target and its transitive
dependencies.
By remembering just the error message as a string, and not the full
exception object, this also helps TransitiveTraversalValue have more
consistent equality semantics for change-pruning.
--
MOS_MIGRATED_REVID=105977182
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105975871
|
|
|
|
|
|
|
|
| |
The cost-benefit isn't there to pay a square cost to roll these up on
the blaze side. Android Studio has to do it on its end instead.
--
MOS_MIGRATED_REVID=105971068
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105969015
|