| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Replace uses of $SDKROOT and $DEVELOPER_DIR values in compile paths with __DEVELOPER_DIR__ and __SDKROOT__ to that xcrunwrapper can deal with them appropriately.
RELNOTES:none
--
MOS_MIGRATED_REVID=107259512
|
|
|
|
|
|
|
|
|
|
|
| |
@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
|
|
|
|
|
|
|
|
|
| |
them to scripts instead of java apps.
RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=104225062
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
generating
the environment's plist.
The script no longer parses the values from the Platform's Info.plist, which contained
the values used to compile the Platform's library *itself*, rather than the values
of the actual running environment.
Also the BuildMachineOSBuild is being read from the sw_version, rather than
the Xcode's plist, and the DTSDKBuild is determined by the plist under sdk-path.
An example environment.plist:
{
BuildMachineOSBuild = 14F27;
DTCompiler = "com.apple.compilers.llvm.clang.1_0";
DTPlatformBuild = 12H141;
DTPlatformVersion = "8.4";
DTSDKBuild = 12H141;
DTXCodeBuild = 6E35b;
DTXcode = 0640;
}
--
MOS_MIGRATED_REVID=103079006
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102345101
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this script, the easiest way to run the test suite is now:
bash -c "export ANDROID_SDK_PATH=$HOME/bin/android-sdk-linux; \
export ANDROID_NDK_PATH=$HOME/bin/android-ndk-r10e; \
source ./scripts/ci/build.sh; \
bazel_build output/ci"
--
MOS_MIGRATED_REVID=102334239
|
|
|
|
|
|
|
| |
Currently only building them is tested, not running them or mobile-install, but it's still a good start.
--
MOS_MIGRATED_REVID=102237496
|
|
|
|
|
|
|
| |
Fixes #262.
--
MOS_MIGRATED_REVID=101126149
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100083317
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaking builds. []
*** Original change description ***
RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=99742398
|
|
|
|
|
|
|
| |
bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=99521906
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks most of the iOS targets on our continuous build.
*** Original change description ***
Move actoolzip, momczip and swiftstdlibtoolzip to tools/xcode and convert them to scripts instead of java apps.
RELNOTES: actoolzip, momczip and swiftstdlibtoolzip have all been made into bash scripts and have been renamed to actoolwrapper, momcwrapper and swiftstdlibtoolwrapper respectively. The old versions will be deleted in a later change.
--
MOS_MIGRATED_REVID=98716081
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=98347349
|
|
|
|
|
|
|
|
|
| |
Fix for https://github.com/google/bazel/issues/300.
RELNOTES:none
--
MOS_MIGRATED_REVID=98230557
|
|
|
|
|
|
|
| |
Adds a jar output to Java and Android rules which contains the class files for source files generated from Java annotation processors. For a java_binary foo, the jar will be foo-gen.jar, and for a java_library foo the jar will be libfoo-gen.jar, and similarly for Android. Also adds a binary serialized proto manifest file output to Java and Android rules which describes the contents of the output class jar of those rules, which is used to create the -gen.jar. See src/main/protobuf/java_compilation.proto.
--
MOS_MIGRATED_REVID=97793715
|
|
|
|
|
|
|
|
|
|
| |
Moves ibtoolzip from being java based to being bash based for easier dev/testing.
Changes the name of ibtoolzip to ibtoolwrapper to avoid conflicts with currently deployed bazel depending on the ibtoolzip name.
Updates realpath
Cleans up update_binaries.sh
--
MOS_MIGRATED_REVID=97724252
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you already ran the deterministic test with an earlier version of
the depot, the second run would build only once Bazel and use the
previous run log to do the diff, leading to an obvious failure as
the code did change. It was due to an incorrect parameter default
value that pointed to the diff of the previous run, skipping the
first bazel compilation.
--
MOS_MIGRATED_REVID=97399620
|
|
|
|
|
|
|
|
|
| |
our tools (ibtool, actool etc) to shell scripts which should be faster and easier to maintain.
RELNOTES:
--
MOS_MIGRATED_REVID=97263085
|
|
|
|
|
|
|
| |
And get rid of usage of "blazerc" flags in our scripts.
--
MOS_MIGRATED_REVID=96776423
|
|
|
|
|
|
|
|
|
| |
This resulted in most of the time on doing only one compilation and comparing
with the previous checksum of generally a older build, making the deterministic
test fails weirdly.
--
MOS_MIGRATED_REVID=96769326
|
|
|
|
|
|
|
|
|
|
| |
This way we can use it to build unstamped binary with an empty
EMBED_LABEL.
--
Change-Id: Id63360f2ccd85a4ba42d54ba670c53cbadacfeca
Reviewed-on: https://bazel-review.googlesource.com/#/c/1560/
MOS_MIGRATED_REVID=96764907
|
|
|
|
|
|
|
| |
Also fix the OS X travis build file.
--
MOS_MIGRATED_REVID=96683399
|
|
|
|
|
|
|
|
|
| |
stdin,stdout,stderr.
A full example of its usage is in RunTests.sh.
--
MOS_MIGRATED_REVID=96319787
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Swift sources whitelisted
* Swift compilation and module merging actions
* Swift stdlib copying into IPA action
* Special case for signing embedded swift stdlib dylibs during bundle signing
* Works with mixed ObjC/Swift sources
* Doesn't support working with dependencies from Swift code.
* Requires Xcode 6.3.1 for swift compiler and tooling.
--
MOS_MIGRATED_REVID=96141887
|
|
|
|
|
|
|
|
| |
This is a replay of the changes from https://bazel-review.googlesource.com/#/c/1520
and that didn't got imported on the import CL.
--
MOS_MIGRATED_REVID=96099800
|
|
|
|
|
|
|
|
|
|
| |
This will allow system-wide configuration for system-wide
installation of Bazel.
--
Change-Id: I71b7232e648f2690766c3b9184f863dc888524c0
Reviewed-on: https://bazel-review.googlesource.com/#/c/1540/
MOS_MIGRATED_REVID=95994630
|
|
|
|
|
|
|
|
|
| |
running system.
Tested on OS X 10.10, Debian 8.1 (x86_64) and Debian 8.1 (i686).
--
MOS_MIGRATED_REVID=95819163
|