| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
repository.
Closes #4860.
Change-Id: I1689fee013d031253d5e55343be174aaa6e638c1
PiperOrigin-RevId: 189588855
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Respect the user-defined TMPDIR, or use TMP or
TEMP on Windows. Since MSYS sets TMP and TEMP to
"/tmp" which is actually "<msysroot>/tmp" (e.g.
"c:\tools\msys64\tmp"), it is shorter than the
Windows-default TEMP directory.
This buys us a bit of headroom to not hit path
length limits while bootstrapping.
Fixes https://github.com/bazelbuild/bazel/issues/4536
Change-Id: I2ab04e3c1c96bc306ef54348cc0c0c2f3fda13ee
PiperOrigin-RevId: 183826475
|
|
|
|
|
| |
Change-Id: I4ea57252dfa2fe0d1386206ee2136beb9d61f7b0
PiperOrigin-RevId: 178092027
|
|
|
|
|
|
|
|
|
| |
The latest version of re2 contains fixes that makes it compatible with new changes in Bazel.
Fixes #4233
RELNOTES: None.
PiperOrigin-RevId: 178087275
|
|
|
|
| |
Change-Id: I4ea57252dfa2fe0d1386206ee2136beb9d61f7b0
|
|
|
|
|
| |
RELNOTES: The --host_platform and --platform flags are no longer experimental.
PiperOrigin-RevId: 177863761
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also:
- check as the first thing in compile.sh that we
can locate the GNU coreutils, and remove the
duplicate check for the same thing on Windows
- check early in compile.sh that we can access
python.exe
Fixes https://github.com/bazelbuild/bazel/issues/3863
Change-Id: Ib48b405cf93eafd48e21b280bcbab4d45117c1d9
PiperOrigin-RevId: 171291435
|
|
|
|
|
|
|
|
| |
PlatformConfiguration is made a legal configuration fragment for every rule class.
Add a default "dummy" c++ toolchain to prevent resolution errors when legacy toolchain selection logic is used. Add toolchain mocks to java and shell tests.
PiperOrigin-RevId: 167901210
|
|
|
|
|
|
|
|
| |
So compile.sh is dedicated to bootstrapping Bazel.
It has been a long time we are not testing those code path anymore and providing a bazel binary on the command line was regularly broken
PiperOrigin-RevId: 166827487
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reportedly, which is not installed by default on all non-windows
systems bazel is used. As we only use which to test if a program
can be found on PATH, use the bash builtin hash command. While there
- replace the search for [ by a search for tr, a program we care more,
as [ is the builtin test anyway,
- fix a typo in the name of the GNU tools collection searched for.
Change-Id: Id78737eba10e96c6fa41ca68a47102ab28e6031f
PiperOrigin-RevId: 166685117
|
|
|
|
|
|
|
|
|
| |
- Test if hash(bazel1) == hash(bazel2)
This ensure that the build of bazel is a fixed point.
Change-Id: I422dfc7ec5b95aa054a2677e59427cbd8cd4ef01
PiperOrigin-RevId: 166180529
|
|
|
|
|
|
| |
...as they are actually useful when debugging.
PiperOrigin-RevId: 163698478
|
|
|
|
|
| |
RELNOTES:
PiperOrigin-RevId: 162914414
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on output of static analysis tool.
https://github.com/koalaman/shellcheck/wiki/SC2166
https://github.com/koalaman/shellcheck/wiki/SC2207
https://github.com/koalaman/shellcheck/wiki/SC2145
https://github.com/koalaman/shellcheck/wiki/SC2001
https://github.com/koalaman/shellcheck/wiki/SC2129
https://github.com/koalaman/shellcheck/wiki/SC2128
https://github.com/koalaman/shellcheck/wiki/SC2004
https://github.com/koalaman/shellcheck/wiki/SC2048
Closes #3162.
PiperOrigin-RevId: 160261247
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 154836224
|
|
|
|
|
| |
Change-Id: I32f6b16955ecefc242af8d9261418452d698c9ff
PiperOrigin-RevId: 154812955
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can't yet fully bootstrap Bazel on Cygwin, but
can build Bazel from scratch. Building Bazel with
Bazel fails because gcc isn't found where it's
believed to be -- /usr/bin is a mount in Cygwin
(to /bin), not a symlink or directory.
In this change I:
- added support for the Cygwin shell as a
bootstrap platform (recognize `uname`)
- updateed the bootstrap scripts to use "windows"
as the PLATFORM string, not "mingw"
- fixed the git lookup code
- removed some hardwired msys-style path
- added a cygpath call to convert $PWD to a
mixed-style (otherwise the bootstrap script
passes --client_cwd=/cygdrive/c/... to the
server and WindowsFileSystem.java wants to make
that relative to c:/cygwin64)
See https://github.com/bazelbuild/bazel/issues/2885
Change-Id: Icc71261ea4f0c6d4a9c0846551a7977ca6020331
PiperOrigin-RevId: 154273014
|
|
|
|
|
|
|
|
|
|
|
|
| |
As of Bazel 0.4.5, the android_sdk_for_test and android_ndk_for_test are bound in android.WORKSPACE, so we do not need to include them in the main Bazel WORKSPACE file. I've update the comments to reflect that all that is needed to run the tests is android_sdk_repository and android_ndk_repository and the environment variables that they read.
Also, delete scripts/workspace_user.sh. All of its functionality (reading environment variables, detecting api levels, build tools versions) is now part of android_{s,n}dk_repository.
Fixes https://github.com/bazelbuild/bazel/issues/2284.
--
PiperOrigin-RevId: 151032551
MOS_MIGRATED_REVID=151032551
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, a msys bazel can be built with
a MSVC-default Bazel by adding --cpu=x64_windows_msys --host=x64_windows_msys
See https://github.com/bazelbuild/bazel/issues/2627
--
Change-Id: Iaa82bf4dd911c5740b98d3b2739dfccca6203f79
Reviewed-on: https://cr.bazel.build/9293
PiperOrigin-RevId: 149532274
MOS_MIGRATED_REVID=149532274
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In this change:
(1) add a sanity check to verify that GNU bintools
are on the PATH
(2) correct the PATH on Windows if (1) failed
(3) use "<user>/My Documents/Temp" as the default
temp directory instead of "%windir%/Temp", because
the latter is non-writable
Motivated by:
https://github.com/bazelbuild/bazel/issues/2431
https://github.com/bazelbuild/bazel/issues/2449
--
PiperOrigin-RevId: 146006796
MOS_MIGRATED_REVID=146006796
|
|
|
|
|
|
|
|
|
|
|
| |
Maybe fixes #1552.
Closes #2175.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2175
PiperOrigin-RevId: 141060731
MOS_MIGRATED_REVID=141060731
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The compile.sh script contains a test verifying that all
sources of Bazel are contained in the //:srcs target. As
reference, the list of files reachable from the top-level
directory is taken. In this check, ignore all derived sources,
i.e., the content of the derived subdirectory to make this test
pass as well when executed from the distribution artifact.
--
Change-Id: I590bc9f424ed5b9f87ed07166ecb75b5aeac9fb3
Reviewed-on: https://bazel-review.googlesource.com/#/c/7136
MOS_MIGRATED_REVID=138884271
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When `compile.sh` builds bazel using bazel, it
copies the resulting binary to `output/bazel`.
However sometimes the convenience symlink
`bazel-bin` is not created, probably because an
old one is still around and cannot be deleted.
That is clearly a bug, but to work around it, the
bootstrap builder shouldn't attempt to rely on the
creation of these symlinks in the first place.
This change updates compile.sh to use `bazel info`
to locate the `bazel-bin` directory's real path,
and attempt to copy the bazel binary from there.
This works around
https://github.com/bazelbuild/bazel/issues/1827
--
MOS_MIGRATED_REVID=134398451
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollback, broke Bazel bootstrap on OS X.
--
MOS_MIGRATED_REVID=132422954
|
|
|
|
|
|
|
|
|
| |
This means that in the absence of "--config=" (or the "--cpu=" and "--ios_cpu=" flags that it indicates), c++ code using //tools/osx/crosstool will default to being built for ios_x86_64 instead of darwin_x86_64.
This is necessary to ensure that once the crosstool is used for objc, the default behavior of objc_library building for ios_x86_64 will be maintained.
--
MOS_MIGRATED_REVID=132326009
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the bootstrapping process so that setting the BAZEL_WRKDIR
environment variable will tell the bootstrap process to mostly write
to that directory---apart from adding the symlinks next to the WORKSPACE
file. So setting this variable will avoid the usual writes to random
places in the file system (like /tmp and the user's home directory).
--
Change-Id: I9d1af747e75cc2a7bb1af08308acc9dfd927e920
Reviewed-on: https://bazel-review.googlesource.com/#/c/3963
MOS_MIGRATED_REVID=127075535
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126571069
|
|
|
|
|
|
|
|
|
|
|
| |
missing file to it.
We need to activate this check on presubmits
--
Change-Id: Ia95e92d3816ce92bb69bc0e2cf56e9c60b68d970
Reviewed-on: https://bazel-review.googlesource.com/#/c/3949/
MOS_MIGRATED_REVID=126404792
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Along the path, fix the build for JDK 7 and get rid of
most ugliness in the JDK 7 build. Now simply setting
JAVA_VERSION to 1.7 will build a JDK 7 compatible version.
Fixes #1159.
--
Change-Id: I9599283844a57d9e053f12d37445907f22a9232e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3452
MOS_MIGRATED_REVID=120332747
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io
While the basics for fixing the build is easy (just a few typos in packages building), fixing the test is a bit more tricky. I see only one solution for fixing the test: use a select statement that would select the good bazel version but that would always pull JavaBuilder as an external dependency when we do test.
Better roll this back then check the JavaBuilder 0.1.0 as a binary in third_party before rolling forward (a similar change is still needed to decouple running the test and building the binary for JDK 7)
*** Original change description ***
Refactor build for JDK 7
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
MOS_MIGRATED_REVID=119773123
|
|
|
|
|
|
|
|
|
|
|
| |
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
Change-Id: Iff590c6642ca5b2343aa15096f8fd837d1c80787
Reviewed-on: https://bazel-review.googlesource.com/#/c/3327
MOS_MIGRATED_REVID=119634530
|
|
|
|
|
|
|
|
|
|
|
| |
All Bazel should now contain the latest version with a date
modifier to ensure we can track all Bazel builds out there.
It is especially important for #1014.
--
Change-Id: I8d17d9e1660b104c2b8623d5a8a06d010d044ea7
Reviewed-on: https://bazel-review.googlesource.com/3070
MOS_MIGRATED_REVID=117120584
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename run_silent to run and add a global VERBOSE variable that tunes
whether the run function prints its output or not.
This is for better debugging possibilities of Bazel's self-build, though
compile.sh remains silent as before and only displays the command's output
in case of an error.
--
MOS_MIGRATED_REVID=115599355
|
|
|
|
|
|
|
|
|
| |
They have now moved to https://github.com/bazelbuild/scala_rules
RELNOTES[INC]: Scala rules were deleted from the @bazel_tools repository, see https://github.com/bazelbuild/rules_scala#scala-rules-for-bazel
--
MOS_MIGRATED_REVID=115432354
|
|
|
|
|
|
|
| |
Needed for #276.
--
MOS_MIGRATED_REVID=114693711
|
|
|
|
|
|
|
| |
--
Change-Id: If286a9718e036d2bd555baf78600e9208ba5a990
Reviewed-on: https://github.com/bazelbuild/bazel/pull/872
MOS_MIGRATED_REVID=114563576
|
|
|
|
|
|
|
| |
Fixes #832.
--
MOS_MIGRATED_REVID=113537330
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
This will create a non-dummy XML file for all our java_test.
--
MOS_MIGRATED_REVID=112449480
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
This method is used only once now so inline.
--
MOS_MIGRATED_REVID=112396086
|
|
|
|
|
|
|
| |
tools command was removed from compile.sh
--
MOS_MIGRATED_REVID=111848422
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
| |
tools/jdk are not necessary anymore.
Fixes #508.
--
MOS_MIGRATED_REVID=108123264
|