| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101462664
|
|
|
|
|
|
|
| |
resolve the file even while outside a workspace which contains it
--
MOS_MIGRATED_REVID=101462428
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
| |
is Linux, do real auto-detection whether it is supported on the host or not and enable / disable it based on the result.
The warning that is printed when the Linux kernel is too old to support sandboxing can be disabled via a flag.
--
MOS_MIGRATED_REVID=101461120
|
|
|
|
|
|
|
|
|
|
| |
Rename some methods to avoid clashes.
Add function formattable to create lazily-formatted objects,
remove now unused strFormattable and reprFormattable.
Also some whitespace cleanup.
--
MOS_MIGRATED_REVID=101459565
|
|
|
|
|
|
|
| |
syscall.
--
MOS_MIGRATED_REVID=101458944
|
|
|
|
|
|
|
|
|
| |
generator_name and generator_function.
Additionally, both Skylark macros and build extensions set the attribute generator_location in order to store the name of the file where generator_function was defined.
--
MOS_MIGRATED_REVID=101458757
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101458091
|
|
|
|
|
|
|
|
|
|
|
|
| |
use non-declared inputs) and safety (spawns can no longer affect the host system, e.g. accidentally wipe your home directory). This implementation works on Linux only and uses Linux containers ("namespaces").
The strategy works with all actions that Bazel supports (C++ / Java compilation, genrules, test execution, Skylark-based rules, ...) and in tests, Bazel could successfully bootstrap itself and pass the whole test suite using sandboxed execution.
This is not the default behavior yet, but can be activated explicitly by using:
bazel build --genrule_strategy=sandboxed --spawn_strategy=sandboxed //my:stuff
--
MOS_MIGRATED_REVID=101457297
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101457236
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101456399
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that Bazel finds Android tools and update the tools themselves to handle their new location.
This paves the way for eventually referencing every tool this way.
We have to figure out if android_http_tools_repository is the right way to distribute the Android tools, but now that we don't have a binary distribution yet, it's not an immediate problem.
This will break existing users of Android support in Bazel, whom I'll inform over bazel-discuss.
Fixes #384.
--
MOS_MIGRATED_REVID=101456190
|
|
|
|
|
|
|
|
| |
- "AppEngine" to "App Engine" as per https://cloud.google.com/appengine/docs
- "WebApplication" to "Java web application" or "web application" as per http://docs.oracle.com/javaee/6/tutorial/doc/geysj.html
--
MOS_MIGRATED_REVID=101454871
|
|
|
|
|
|
|
| |
crate_features to fix conflict with new default features attribute.
--
MOS_MIGRATED_REVID=101454678
|
|
|
|
|
|
|
|
| |
Each of the support rule sets now have their own README.md files. This page just links
to the directories in the repo where the rules are located and documented.
--
MOS_MIGRATED_REVID=101453919
|
|
|
|
|
|
|
|
|
| |
All affected rules were annotated, and all known affected Skylark rules were
also annotated. The documentation was updated, so it looks like we're good
to go.
--
MOS_MIGRATED_REVID=101450297
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101446590
|
|
|
|
|
|
|
| |
It rotted somewhere along the way and tried to build Objective C tools on Linux, and unsurprisingly, failing.
--
MOS_MIGRATED_REVID=101445358
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101388809
|
|
|
|
|
|
|
|
| |
In practice there are generally very few of these, keep a chache
to avoid dups.
--
MOS_MIGRATED_REVID=101386883
|
|
|
|
|
|
|
| |
looking for the .runfiles path and the Python interpreter binary.
--
MOS_MIGRATED_REVID=101380117
|
|
|
|
|
|
|
| |
implementations.
--
MOS_MIGRATED_REVID=101379672
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101377320
|
|
|
|
|
|
|
| |
SkylarkEnvironment's recursion detection.
--
MOS_MIGRATED_REVID=101374341
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, shared objects in the transitive closure of an Android binary would be linked
in, but not be sent to the apkbuilder. This sends all the shared objects used for linking
to join the other native libraries in the APK, so they will be loadable when the main
library created by the link step is loaded.
Fixes #357.
--
MOS_MIGRATED_REVID=101365491
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101364893
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101363350
|
|
|
|
|
|
|
|
|
| |
//external: targets can depend on anything and visibility is checked a the edges incoming to said labels.
Fixes #388.
--
MOS_MIGRATED_REVID=101363086
|
|
|
|
|
|
|
| |
Fixes #360.
--
MOS_MIGRATED_REVID=101360551
|
|
|
|
|
|
|
|
|
|
| |
The mechanism was easy to workaround (store the object in a different
variable) and a source of bugs. This affected only 'rule', 'native' and
'attr' objects. It turns out the blacklisting was not useful (native and
attr are already filtered, rule is not a problem).
--
MOS_MIGRATED_REVID=101359277
|
|
|
|
|
|
|
| |
(and 2.12).
--
MOS_MIGRATED_REVID=101358929
|
|
|
|
|
|
|
| |
the documentation.
--
MOS_MIGRATED_REVID=101357875
|
|
|
|
|
|
|
|
| |
We will lock down that only specified fragments may be accessed, but
submitting that is blocked on all existing rules declaring fragments correctly.
--
MOS_MIGRATED_REVID=101352316
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101348687
|
|
|
|
|
|
|
| |
ctx.fragments.{cpp,java,jvm} instead.
--
MOS_MIGRATED_REVID=101348294
|
|
|
|
|
|
|
| |
artifact with the given name instead of appending a suffix
--
MOS_MIGRATED_REVID=101348273
|
|
|
|
|
|
|
|
|
|
| |
This is an easy way to deal with other code that names scripts as such,
rather than requiring that scripts be renamed to end in ".lds"
RELNOTES[NEW]: deps of a cc_binary may contain linker script files ending in ".ldscript"
--
MOS_MIGRATED_REVID=101346375
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101346366
|
|
|
|
|
|
|
|
|
|
|
| |
big fat warning that that
method shouldn't be used anymore.
Ideally, I'd mark it as deprecated, but it's legitimately used by RuleContext. I could just forbid access to AnalysisEnvironment to rule implementations, but, sadly, almost every method on it is called at a few oddball places in implementations of various rules, so we can't do it just yet.
--
MOS_MIGRATED_REVID=101345484
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101344826
|
|
|
|
|
|
|
| |
The build-in rules also use it.
--
MOS_MIGRATED_REVID=101343109
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101245691
|
|
|
|
|
|
|
| |
Use stripped launcher when Fission is enabled.
--
MOS_MIGRATED_REVID=101244628
|
|
|
|
|
|
|
| |
RELNOTES: For Objective-C make -DDEBUG part of the -c fastbuild options
--
MOS_MIGRATED_REVID=101243825
|
|
|
|
|
|
|
|
|
|
| |
Don't expect FLOW events if the compile policy is set to stop before FLOW
(e.g. with -proc:only).
Fixes google/bazel#379
--
MOS_MIGRATED_REVID=101242866
|
|
|
|
|
|
|
| |
getAllowedDeps calls on the same batch call
--
MOS_MIGRATED_REVID=101238126
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101235139
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101233095
|
|
|
|
|
|
|
|
|
| |
specifying the
class of the provider object.
--
MOS_MIGRATED_REVID=101227127
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101221537
|