| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
Leave functions that make file accesses in the file library, and general blaze utilities in the blaze_util file, but move the functions that boil down to string manipulation and path formatting to their own file. (With the exception of getCWD, since absolute path syntax is relevant here.)
Doing this largely to consolidate all Windows path control into a single place, so that it's easier to notice inconsistencies. For instance, ConvertPath currently makes Windows paths absolute, but not Posix paths, and MakeAbsolute relies on this behavior. In addition, JoinPath assumes Posix path syntax, which leads to some odd looking paths. These will be fixed in a followup change.
(Found these issues while working on #4502, trying to fix the windows-specific system bazelrc.)
RELNOTES: None.
PiperOrigin-RevId: 199368226
|
|
|
|
|
|
|
| |
This will mean the messages will make it to the right output stream.
RELNOTES:
PiperOrigin-RevId: 191925662
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 181149284
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
FreeBSD should work again, so re-enable it.
*** Original change description ***
Remove FreeBSD from our CI temporarily.
RELNOTES: None.
PiperOrigin-RevId: 181140165
|
|
|
|
| |
Change-Id: Ic3d2331b7ccb5ca7db6b0fe83a12c7a6d1b58a9a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll forward of commit 86b4532769c22cca2ed7068a60f3326beaad34af after fixing bad import.
+small misc fixes suggested by critique
*** Original change description ***
Automated rollback of commit 86b4532769c22cca2ed7068a60f3326beaad34af.
*** Reason for rollback ***
Probably breaking //javatests/com/google/devtools/build/lib:Query2Tests
*** Original change description ***
Restructure how universeScope is used when testing configured query to mimick impending changes to the configured query interface (CL/179872445) which will pull build targets out of the query expression.
Fill in testTopLevelTransitions on the way!
PiperOrigin-RevId: 180930388
|
|
|
|
| |
Change-Id: I14256e583d07ebad9a0b525917d25e5cb5f7f684
|
|
|
|
|
|
|
|
|
|
| |
Please refer to patch set 9 and its CI run for usage and test
results. In practice, users should create their own java_toolchain
rule in their project's BUILD file, and set the two attributes like
above instead of modifying //tools/jdk/BUILD.
Change-Id: Ic880f243086b00a58d453a8139ba4c957fe54bc7
PiperOrigin-RevId: 159694649
|
|
|
|
|
|
|
|
|
|
|
| |
This affects only the tuple that appears after 'if' inside a list
comprehension. Since a truth value is expected, it's very unlikely to break
existing code. It's technically a breaking change, but it's not worth
introducing a flag for this.
RELNOTES:
Parentheses around the tuple are now mandatory in [a for b in c if 1, 2]
PiperOrigin-RevId: 159218397
|
|
|
|
|
|
| |
This is part of https://bazel-review.googlesource.com/#/c/11590/.
Change-Id: Id4a7fd459013e3f25a5a99684ea04295e3b68fb4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Fixed all errors.
*** Original change description ***
Automated [] rollback of commit 69a127b8f4e353ecb163688ed3271fb47e0f385d.
--
PiperOrigin-RevId: 149092038
MOS_MIGRATED_REVID=149092038
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
[] has detected that 500 or more targets failed to build at commit 69a127b8f4e353ecb163688ed3271fb47e0f385d, each of which successfully built at the prior CL that affected them.
[] double-checked that //javatests/com/google/apphosting/tests/usercode:Security_StubTest
built at 148995024. The verification run was:
[]
but the same target failed to build at 148995025. The [] link for this run is available here: []
To see all targets that ran, along with their final status, visit: []
Questions? Comments? See the URL.
go/autorollback
*** Original change description ***
ijar: use bazel's file utilities
This change not only implements ijar for Windows
(with MSVC), but also fixes a bug in
mapped_file_windows (path conversion didn't make
the input path absolute, so we could not build
java code with the MSYS-less bazel).
Fixes https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148998092
MOS_MIGRATED_REVID=148998092
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change not only implements ijar for Windows
(with MSVC), but also fixes a bug in
mapped_file_windows (path conversion didn't make
the input path absolute, so we could not build
java code with the MSYS-less bazel).
Fixes https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148995025
MOS_MIGRATED_REVID=148995025
|
|
|
|
|
|
|
|
| |
See https://github.com/bazelbuild/bazel/issues/2157
--
PiperOrigin-RevId: 148887981
MOS_MIGRATED_REVID=148887981
|
|
|
|
|
| |
PiperOrigin-RevId: 148768294
MOS_MIGRATED_REVID=148768294
|
|
|
|
|
|
| |
Commit 6d31cb was an internal reorganization of google repository
that should have resulted in no change. Due to a bug in our export
process it deleted several files in third_party.
|
|
|
|
|
| |
PiperOrigin-RevId: 142666783
MOS_MIGRATED_REVID=142666783
|
|
|
|
|
|
|
|
|
|
| |
This change takes us closer to compiling ijar,
thus Bazel, with MSVC.
See https://github.com/bazelbuild/bazel/issues/2107 and https://github.com/bazelbuild/bazel/issues/2157
--
MOS_MIGRATED_REVID=140717828
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Other projects may depend on Ijar without wanting to depend on Bazel.
*** Original change description ***
Ijar: use utilities from Bazel's source
Remove a duplicate implementation of JoinPath.
--
MOS_MIGRATED_REVID=135088616
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Other projects may depend on Ijar without wanting to depend on Bazel.
*** Original change description ***
Ijar: use more utilities from Bazel's source
Remove duplicate implementations from zip_main.cc
--
MOS_MIGRATED_REVID=135086722
|
|
|
|
|
|
|
| |
Remove duplicate implementations from zip_main.cc
--
MOS_MIGRATED_REVID=134797116
|
|
|
|
|
|
|
| |
Remove a duplicate implementation of JoinPath.
--
MOS_MIGRATED_REVID=134778185
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update `select` statements in BUILD files with the
new config_setting.
This is a first step on a long path that leads to
us being able to compile bazel on Windows with
--cpu=x64_windows_msvc. Needless to say, we're not
there yet.
Tested: on Linux, Darwin, Windows/MSYS
--
MOS_MIGRATED_REVID=134534613
|
|
|
|
|
|
|
| |
class. And add a dummy zlib client.
--
MOS_MIGRATED_REVID=133879880
|
|
|
|
|
|
|
| |
This was the last dependency of Bazel that is pulled in from the host system, so now (at least as dependencies go) the source tree of Bazel is now self-contained.
--
MOS_MIGRATED_REVID=119243670
|
|
|
|
|
|
|
|
| |
This target include all non tests targets of Bazel to do integration tests of
bootstrapping.
--
MOS_MIGRATED_REVID=115830741
|
|
|
|
|
|
|
|
|
|
| |
Instead bundle ijar's zipper binary so the skylark rules that depends on it
can use it from @bazel_tools.
A commit introducing windows config settings broke our appengine tutorial.
--
MOS_MIGRATED_REVID=114857080
|
|
|
|
|
|
|
| |
Progress towards #276.
--
MOS_MIGRATED_REVID=114829911
|
|
|
|
|
|
|
| |
Progress on #276.
--
MOS_MIGRATED_REVID=114740700
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With those filegroup the tutorial is able to compile iOS and
App Engine stuff. Here how to test:
git clone https://github.com/bazelbuild/bazel
git clone https://github.com/bazelbuild/examples
export BAZEL_WORKSPACE=$PWD/bazel
export EXAMPLES_WORKSPACE=$PWD/examples
cd $BAZEL_WORKSPACE
./compile.sh
./output/bazel --bazelrc=/dev/null --nomaster_bazelrc \
build //scripts/packages:install.sh
export BAZEL_INSTALLER=$(readlink bazel-bin)/scripts/packages/install.sh
cd $EXAMPLES_WORKSPACE
./tutorial/ci/build.sh
--
Change-Id: I553ab8821f5a5cdcc7a8b4614e23ca4c79581e4f
Reviewed-on: https://bazel-review.googlesource.com/1878
MOS_MIGRATED_REVID=102239866
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now the blessed Bazel binary is self-hosted and correctly labeled.
All tools are also built using Bazel and labeled with the release.
At the end of the compilation, the output folder only host the
Bazel binary now. We use temporary folders to store the intermediate
artifacts.
Also integrated ./bootstrap_test.sh in compile.sh so there is only
one script for everything regarding bootstraping Bazel.
--
Change-Id: Idadbd075e7b8ecb6e306b919b7a73c647c5cfbae
Reviewed-on: https://bazel-review.googlesource.com/#/c/1460/
MOS_MIGRATED_REVID=95625880
|
|
|
|
|
|
|
|
|
|
|
| |
This ZIP implementation is lightweight and rely on zlib for
compression. libarchive was a bit tricky to set-up so it's
better to use that one.
--
Change-Id: I607b492998572e834e095a4606eeb77c0b574542
Reviewed-on: https://bazel-review.googlesource.com/#/c/1410/
MOS_MIGRATED_REVID=94910072
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It extracts Zip/Unzip methods of ijar in a separate
library. A zipper binary is provided to test that
implementation outside. Note that this implementation
does not compute CRC-32 and unzip will complain on
file zipped with it (but Java won't complain).
The error handling has been replaced to use proper error
reporting instead of launching abort()'s allover the place
so ijar's zip library can be used outside of ijar.
Finally, support for ZIP preamble has been added to
handle self-extractable ZIP files.
--
Change-Id: I833034b4c0054925bada75102fe040db875da789
Reviewed-on: https://bazel-review.googlesource.com/#/c/1371/
MOS_MIGRATED_REVID=94656262
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=88210083
|
|
--
MOE_MIGRATED_REVID=85702957
|