| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* We already have native python rules, so the skylark
ones are no longer unnecessary now
* Leaving `load skylark rules` statement in the example
may be misleading for newcomers
Testing done:
* re-compile bazel
* use it to build example folder and run py target
``` shell
./compile.sh compile /usr/bin/bazel
/home/yiyu/opt/bazel/output/bazel build //examples:all
/home/yiyu/opt/bazel/output/bazel run //examples/py:bin
```
--
Change-Id: Icd82afff2b74e77c0bcc80687b04225baf28f6ad
Reviewed-on: https://cr.bazel.build/9070
PiperOrigin-RevId: 148646895
MOS_MIGRATED_REVID=148646895
|
|
|
|
|
|
|
|
|
| |
This is in preparation for another change that will add a new helper script
to the tools/build_rules directory, and such script requires a BUILD rule
of its own.
--
MOS_MIGRATED_REVID=114898083
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will fix some issue with loading skylark rules from @bazel_tools.
Tested with ./compile.sh all and also a project that use pkg_tar from
@bazel_tools (which is broken at HEAD).
--
Change-Id: Iffbb7134ef5fee497890c4d01b85084973d45ad0
Reviewed-on: https://bazel-review.googlesource.com/2800
MOS_MIGRATED_REVID=113508661
|
|
|
|
|
|
|
|
|
|
|
| |
If the system python interpreter is set to python3, some tests fail
because python3 requires parenthesies for the print statement.
Fix this by adding the required parenthesies, which are a no-op for
python2.
--
Reviewed-on: https://github.com/google/bazel/pull/282
MOS_MIGRATED_REVID=97571926
|
|
|
|
|
|
|
|
|
| |
It is a first batch of integration tests for Bazel. They tests some
basic behaviors and nominal cases of Bazel rules (especially they tests
the behavior of the examples provided in //examples).
--
MOS_MIGRATED_REVID=89440074
|
|
Those examples will be used for Bazel integration tests and their
sources should be available directly to the Bazel workspace itself.
--
MOS_MIGRATED_REVID=89380736
|