| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
we encounter a bad target pattern.
--
MOS_MIGRATED_REVID=111374219
|
|
|
|
|
|
|
|
|
| |
This allows using PY3 binaries in the HOST configuration.
--
Change-Id: I9603bb19a72cb3d0d731de5b35e135ce952cc545
Reviewed-on: https://bazel-review.googlesource.com/2401
MOS_MIGRATED_REVID=111311727
|
|
|
|
|
|
|
|
|
| |
This commit adds proto messages that represent configurable values,
and modifies attribute value serialization code to handle those
values, which are called SelectorLists.
--
MOS_MIGRATED_REVID=111149272
|
|
|
|
|
|
|
| |
for use in tools.
--
MOS_MIGRATED_REVID=111142252
|
|
|
|
|
|
|
| |
import as a PathFragment.
--
MOS_MIGRATED_REVID=111138001
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111130363
|
|
|
|
|
|
|
|
|
| |
adjacent plist read by xcode are identical.
To do this, we use the output of plmerge as the single plist for the bundle. Automatic entries and variable substitutions are both computed in blaze and passed into plmerge. The output of plmerge is passed into bundlemerge to be placed directly into the final bundle.
--
MOS_MIGRATED_REVID=111129433
|
|
|
|
|
|
|
| |
Fixes #742.
--
MOS_MIGRATED_REVID=111043129
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=111032954
|
|
|
|
|
|
|
| |
"default_ios_provisioning_profile"
--
MOS_MIGRATED_REVID=111030705
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110840166
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110838816
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110836326
|
|
|
|
|
|
|
| |
Add some functions to Build, allow method calls.
--
MOS_MIGRATED_REVID=110835163
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110834841
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110797095
|
|
|
|
|
|
|
|
| |
Not the most elegant, but not super intrusive. Can result in extra interned PackageIdentifiers,
but in practice this should be very few.
--
MOS_MIGRATED_REVID=110794705
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel
*** Original change description ***
Ensure that the plist inside an .ipa bundle produced by blaze and the adjacent plist read by xcode are identical.
To do this, we use the output of plmerge as the single plist for the bundle. Automatic entries and variable substitutions are both computed in blaze and passed into plmerge. The output of plmerge is passed into bundlemerge to be placed directly into the final bundle.
--
MOS_MIGRATED_REVID=110792182
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
files in external repositories.
In addition:
- Cleaned up and refactored some tests to reflect the new loading behavior.
Deferred to future CLs:
- Updating Bazel Skylark documentation to reflect the new load form.
- Enabling command-line loading of Aspects via labels.
RELNOTES: 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.
--
MOS_MIGRATED_REVID=110786452
|
|
|
|
|
|
|
| |
Fixes #587.
--
MOS_MIGRATED_REVID=110785300
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110778743
|
|
|
|
|
|
|
|
|
| |
adjacent plist read by xcode are identical.
To do this, we use the output of plmerge as the single plist for the bundle. Automatic entries and variable substitutions are both computed in blaze and passed into plmerge. The output of plmerge is passed into bundlemerge to be placed directly into the final bundle.
--
MOS_MIGRATED_REVID=110770779
|
|
|
|
|
|
|
| |
RELNOTES: Added ability to declare and use aspects in Skylark.
--
MOS_MIGRATED_REVID=110763176
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110709069
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110701982
|
|
|
|
|
|
|
|
|
|
| |
I had to make a small change to ExternalFilesHelper. The Bazel test setup
creates a remote repository for the tools, so we always have external files,
incl. during loading. However, some of the tests don't setup an output
directory, but instead pass null, which would lead to a crash.
--
MOS_MIGRATED_REVID=110669993
|
|
|
|
| |
MOS_MIGRATED_REVID=110484622
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110472320
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110446625
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The original CL broke our CI because Bazel used an old version of Guava (18.0 instead of 19.0). We fixed this problem, so we can roll forward the original change.
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Broke the build: http://ci.bazel.io/job/Bazel/262/
*** Original change description ***
Skylark: implemented more string functions (isalnum, isdigit, etc).
--
MOS_MIGRATED_REVID=110439750
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke the build: http://ci.bazel.io/job/Bazel/262/
*** Original change description ***
Skylark: implemented more string functions (isalnum, isdigit, etc).
--
MOS_MIGRATED_REVID=110383960
|
|
|
|
|
|
|
|
|
| |
will make it easier to manage the transition from legacy Skylark path-style loads to label-based loads. We handle both old-style (path-based) imports and new-style (label-based) imports.
This class is in the cmdline package since it depends on Label-related code in the same package. The cmdline package depends on the syntax package, so this class can't go there, which would otherwise be a reasonable place to put it.
--
MOS_MIGRATED_REVID=110372547
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Skylark into their own package. This allows, e.g., classes in the syntax package to access classes in the cmdline package without creating circular dependencies.
While we're here:
- Removed a couple of unused BUILD deps flagged in [].
- Updated SkylarkRuleImplementationFunctionsTest to remove non-ASCII characters and
clarify the intent of the test.
--
MOS_MIGRATED_REVID=110360763
|
|
|
|
|
|
|
|
| |
Makes "explicitlySpecified" a primitive boolean instead of a boxed
Boolean. Minor formatting changes to ProtoOutputFormatter.
--
MOS_MIGRATED_REVID=110360334
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110358343
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110356954
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110356439
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110348607
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
external/ directory, i.e. were created by Bazel.
This avoids a cycle that arose when a file is load()ed from the WORKSPACE file that is reached through a symlink to an external directory:
* The WORKSPACE file depends on the package lookup node of the .bzl file
* The package lookup node (transitively) depends on wherever the symlink points
* The target of the symlink is an external file and as such, it depends on the WORKSPACE file
This will probably be, erm, interesting to solve when we get as far as to load stuff from external repositories in the WORKSPACE file, but we are just not there yet.
--
MOS_MIGRATED_REVID=110344658
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110280939
|
|
|
|
|
|
|
| |
Native dependencies should be collected from both deps and exports.
--
MOS_MIGRATED_REVID=110279453
|
|
|
|
|
|
|
| |
targets.
--
MOS_MIGRATED_REVID=110275427
|
|
|
|
|
|
|
| |
Type "map" doesn't exist. "struct" is not allowed.
--
MOS_MIGRATED_REVID=110265638
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110261986
|
|
|
|
|
|
|
|
|
|
|
| |
to aapt.
Turns out, it does the wrong thing when using --nodistinct_host_configuration. Not that option should ever be used, but still.
Fixes #523. Probably.
--
MOS_MIGRATED_REVID=110232316
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110174447
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110155243
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110153136
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110141376
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110135504
|