| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=113356411
|
|
|
|
|
|
|
|
|
|
|
| |
On Windows, MSYS will mangle all arguments that resemble Unix paths
when executing (exec*()) non-msys executables (in an attempt to convert
them to Windows paths). This affects ``//src:bazel`` (it becomes
``/src:bazel``) but not ``src:bazel``. This CL converts to the latter in
bootstrapping shell scripts to work around this issue.
--
MOS_MIGRATED_REVID=113349821
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Issue that caused the rollback (#819) is resolved
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
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 //......
--
MOS_MIGRATED_REVID=113259357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
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=113164089
|
|
|
|
|
|
|
|
| |
RELNOTES: JDK-related targets are now available via @local_jdk (instead of
@local-jdk).
--
MOS_MIGRATED_REVID=113067049
|
|
|
|
|
|
|
|
| |
Update buildenv.sh to detect aarch64 as on Nvidias Jetson TX1 as ARM architecture. Final goal is to build tensorflow on jetson tx1
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/814
MOS_MIGRATED_REVID=112967980
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
terminal, not the bazel server.
This fixes two user annoyances:
1) the command can now read from stdin
2) the bazel lock is not held when the command is invoked
The script use's bazel's `--script_path` flag to write out the shell script that runs the command.
--
MOS_MIGRATED_REVID=112815712
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112685830
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
The generated project is not perfect, but this does unblock Manuel for the time being.
--
MOS_MIGRATED_REVID=112571724
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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 remove all C++ compilation in bootstrapping itself.
--
MOS_MIGRATED_REVID=112407516
|
|
|
|
|
|
|
| |
Another step towards no C++ compilation outside of Bazel for bootstrapping.
--
MOS_MIGRATED_REVID=112399835
|
|
|
|
|
|
|
|
| |
process-wrapper is a C++ tool, replacing by a dummy shell version to
reduce the number of C++ compiler calls during the bootstrap process.
--
MOS_MIGRATED_REVID=112398152
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112397181
|
|
|
|
|
|
|
| |
This method is used only once now so inline.
--
MOS_MIGRATED_REVID=112396086
|
|
|
|
|
|
|
|
| |
This simplify the bootstrap process and remove a C++ tool from
the bootstrap binary.
--
MOS_MIGRATED_REVID=112394555
|
|
|
|
|
|
|
|
|
| |
Instead use the current tools from the repository. This
simplifies the bootstrap binary and is a step towards
no C++ compilation for the bootstrap binary.
--
MOS_MIGRATED_REVID=112240524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112239696
|
|
|
|
|
|
|
|
|
| |
Using java8-jdk will match both openjdk-8-jdk and oracle-java8-jdk similarly with java7-jdk. If
either of them are installed on the system allowing bazel to be installed in either case. Also the jdk source is not needed to create the bazel deb pacakge.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/785
MOS_MIGRATED_REVID=112132285
|
|
|
|
|
|
|
|
|
|
| |
0.1.3 was transformed into 0.1.~3 instead of 0.1.3
Tested the regexp manually with:
echo 0.1.3 | sed ...
echo 0.1.3rc3 | sed ...
--
MOS_MIGRATED_REVID=111884245
|
|
|
|
|
|
|
|
|
| |
The installer was missing the StdRedirect.dylib after a recent change.
This was breaking the Tutorial job on ci.bazel.io (and iOS builds using
that installer).
--
MOS_MIGRATED_REVID=111855462
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with fix
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Broke tests on Mac: https://google.com/url?sa=D&q=http%3A%2F%2Fci.bazel.io%2Fjob%2FBazel%2FJAVA_VERSION%3D1.8%2CPLATFORM_NAME%3Ddarwin-x86_64%2F269%2Fconsole
*** Original change description ***
Speed-up bootstrap on OS X by removing tool compilation.
--
MOS_MIGRATED_REVID=111833617
|
|
|
|
|
|
|
| |
For bazel on non-darwin architectures, this will simply be a stub, and should never be invoked. On darwin arcitectures, the tool will map xcode version to xcode path on the host system.
--
MOS_MIGRATED_REVID=111651147
|
|
|
|
|
|
|
| |
bazel server exits abruptly.
--
MOS_MIGRATED_REVID=111641619
|
|
|
|
|
|
|
| |
Fixes #752.
--
MOS_MIGRATED_REVID=111614541
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke tests on Mac: https://google.com/url?sa=D&q=http%3A%2F%2Fci.bazel.io%2Fjob%2FBazel%2FJAVA_VERSION%3D1.8%2CPLATFORM_NAME%3Ddarwin-x86_64%2F269%2Fconsole
*** Original change description ***
Speed-up bootstrap on OS X by removing tool compilation.
--
MOS_MIGRATED_REVID=110785493
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110704529
|
|
|
|
|
|
|
| |
will get rid of all the "ghost flakes" where tests crashed with no apparant reason printed into our logs. Now a stack trace is printed and an easy to understand failure reason, too.
--
MOS_MIGRATED_REVID=110142957
|
|
|
|
|
|
|
| |
This is useful because they have rules that depend on rules in the subpackages of examples and tools thus negating the benefit of not descending into them when running "bazel build //...".
--
MOS_MIGRATED_REVID=109774976
|
|
|
|
|
|
|
|
|
| |
This is a temporary hack until the base workspace goes away.
Fixes #652.
--
MOS_MIGRATED_REVID=109677574
|
|
|
|
|
|
|
|
|
| |
for debian package
Fixes #687
--
MOS_MIGRATED_REVID=109565904
|
|
|
|
|
|
|
| |
Manually tested with `source scripts/ci/build.sh; create_index_html rc2` where rc2 is the folder from 0.1.2rc2.
--
MOS_MIGRATED_REVID=108630774
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108500888
|
|
|
|
|
|
|
| |
annotation processor, and add its output directory to the source tree.
--
MOS_MIGRATED_REVID=108239745
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108029812
|
|
|
|
|
|
|
| |
When output/bazel didn't exist (like in clean checkouts), "./compile.sh compile" would build a bazel without ijar, JavaBuilder_deploy.jar and their friends, which of course didn't work.
--
MOS_MIGRATED_REVID=107772112
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107377319
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was ending up installed as /bazel.
Also, the documented way of telling pkg_tar not to strip off the prefix
didn't work.
--
Change-Id: I593d17690526c614697369cab543aff1ba67de0a
Reviewed-on: https://bazel-review.googlesource.com/#/c/2222/
MOS_MIGRATED_REVID=107229260
|
|
|
|
|
|
|
| |
Bazel builds 4x faster than before, which also speeds up CI and running the test suite.
--
MOS_MIGRATED_REVID=107067655
|
|
|
|
|
|
|
|
|
| |
Avoid depending on extended regexp of gawk
--
Change-Id: I28a57c249c5b8078b410c365f51f400bcdc27997
Reviewed-on: https://bazel-review.googlesource.com/#/c/2240
MOS_MIGRATED_REVID=106877966
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During bootstrap a number of tools are linked manually. These
link steps should take LDFLAGS to bootstrap bazel with custom
toolchain.
These tools are build-runfiles, process-wrapper and
namespace-sandbox.
cc_link() routine in compile.sh already takes LDFLAGS but not
the link steps for the tools listed above. They should all do so.
A developer can now do this to build Bazel:
CC="some-gcc" CXX="some-g++" LDFLAGS="-Lsome-glibc" \
JNI_LD_ARGS="-Lsome-glibc" ./compile.sh
--
Change-Id: Ifd1a03e989266a7fe3f1f92a7a44093b135fdc18
Reviewed-on: https://bazel-review.googlesource.com/2211
MOS_MIGRATED_REVID=106378256
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106307162
|
|
|
|
|
|
|
|
|
| |
back to getpwuid())
Also a minor compatibility fix in a sed invocation.
--
MOS_MIGRATED_REVID=106291639
|
|
|
|
|
|
|
|
|
|
|
| |
@bazel_tools repository.
The fix is to always compile tools when the Bazel binary is compiled and add the bootstrap arguments to bootstrap_test. This stil litters the git client with output files in random places, which is a bit difficult to fix, since //src:bazel expects these files to be there so that it can embed them into the output binary.
I didn't notice this issue because tools/jdk/*_deploy.jar is in the .gitignore file, thus, when "git status" reported nothing, I asumed I ran the build in a clean client.
--
MOS_MIGRATED_REVID=105206124
|
|
|
|
|
|
|
|
| |
Fixes the illegal option error here:
http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=darwin-x86_64/162/console
--
MOS_MIGRATED_REVID=105189685
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105060098
|