| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This cycle was due to JacocoCoverage_deploy.jar being an implicit dependency
of java_binary. We do not need the binary during bootstrap because we are not
running with coverage but we need the target. Simply move it to exists as a
java_import in tools/jdk.
Fixes #2269.
To be cherry-picked for #2246.
--
Change-Id: I63aee0e76b305833ac0c0c2cae5abe1cbad5e6d1
Reviewed-on: https://cr.bazel.build/8036
PiperOrigin-RevId: 142537244
MOS_MIGRATED_REVID=142537244
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141396618
MOS_MIGRATED_REVID=141396618
|
|
|
|
|
|
|
|
|
|
|
|
| |
For some reason still be found, on darwin, the same file
is listed twice on the list of files to be contained in
the embeeded tools. So change every file copied to the
work directory to be writable there. Fixes #2125. But
the question, why the file is mentioned twice there is
still left open.
--
MOS_MIGRATED_REVID=140019860
|
|
|
|
|
|
|
| |
This should now get appropriately embedded into @bazel_tools.
--
MOS_MIGRATED_REVID=134319465
|
|
|
|
|
|
|
|
|
|
|
| |
1) In ExperimentalObjcLibrary, if static linking is required, signal CcLibraryHelper to create a static link action and pass in the necessary variables/link action input.
2) Add a new link type (Link.LinkTargetType.OBJC_STATIC_LIBRARY). This involves changes to Link and LinkCommandLine.
3) For this new link type, implement static linking the OSX CROSSTOOL. Also add tools in the crosstool package that point at libtool, which performs the archiving.
--
MOS_MIGRATED_REVID=130022410
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=128181372
|
|
|
|
|
|
|
| |
reference by future repository rules. Removes the xcode-locator binary file under tools/objc. Originally, the precompiled binary was going to be referenced, but it's easier to build from source in the repository rule.
--
MOS_MIGRATED_REVID=128063694
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is better to use the {} + as it passes the file list to touch instead of calling touch command once for each file. This will reduce the number of times touch process is created and massively speed up the script
From man page
-exec utility [argument ...] {} +
Same as -exec, except that ``{}'' is replaced with as many pathnames as possible for each invocation of utility. This behaviour is similar to that of
xargs(1).
--
MOS_MIGRATED_REVID=125821677
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...and then make it a script for the POSIX shell. This script
is called directly (and not as an argument to the shell), hence
the #!-line needs to be correct. Making it a script for the POSIX
shell has the advantage that the path is canonical.
This is a corrected roll forward of b692917a.
--
Change-Id: I9afa5642ea4c36d944de811135d57b974eefdfff
Reviewed-on: https://bazel-review.googlesource.com/#/c/3852
MOS_MIGRATED_REVID=125670937
|
|
|
|
|
|
|
|
|
| |
is not picked up when you run the scripts manually using "bash script.sh".
This is also in our shell style guide: "Executables must start with #!/bin/bash and a minimum number of flags. Use set to set shell options so that calling your script as bash <script_name> does not break its functionality."
--
MOS_MIGRATED_REVID=125450962
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke Bazel build on Ubuntu 15.10, e.g.:
http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=ubuntu_15.10-x86_64/611/console
*** Original change description ***
Make create_embedded_tools.sh an sh script
This script is called directly (and not as an argument to the shell),
hence the #!-line needs to be correct. As the script does not use any
bash-specific feature, we can maintain it as a script for the POSIX
shell, which has the advantage that the path is canonical.
--
MOS_MIGRATED_REVID=125441679
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=125187340
|
|
|
|
|
|
|
| |
@bazel_tools. Currently the tool still remains in embedded_binaries, but we will migrate away from that: Eventually it can simply live just under @bazel_tools.
--
MOS_MIGRATED_REVID=123436822
|
|
|
|
|
|
|
|
|
|
|
|
| |
This script is called directly (and not as an argument to the shell),
hence the #!-line needs to be correct. As the script does not use any
bash-specific feature, we can maintain it as a script for the POSIX
shell, which has the advantage that the path is canonical.
--
Change-Id: Id1d1d0a4f4516c91fa25cf2402dda5190e618166
Reviewed-on: https://bazel-review.googlesource.com/#/c/3602
MOS_MIGRATED_REVID=122046234
|
|
|
|
|
|
|
|
| |
This allows --experimental_java_header_compilation=true to be used with Bazel.
It is still off by default.
--
MOS_MIGRATED_REVID=121623213
|
|
|
|
|
|
|
|
| |
Once and for all, I tested it and re-tested should
be good.
--
MOS_MIGRATED_REVID=120381352
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
A small step towards the resolution of #276.
--
MOS_MIGRATED_REVID=114330517
|
|
|
|
|
|
|
|
|
| |
Moved RepositoryValue to RepositoryDirectoryValue so that it could be cached
(and not re-downloaded) even if the WorkspaceAST caused a Skyframe restart
(as mentioned in https://github.com/bazelbuild/bazel/blob/master/src/main/java/com/google/devtools/build/lib/rules/repository/RepositoryDelegatorFunction.java#L130-L133).
--
MOS_MIGRATED_REVID=113358489
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112027454
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
| |
The -X option removes UID/GID information from the zip file, which of course is non-hermetic. There is still some weirdness with install_base_key, but I couldn't figure out what that is: the files that are checksummed are always the same and they are in the same order.
--
MOS_MIGRATED_REVID=107484288
|
|
|
|
|
|
|
| |
Should fix build on OSX.
--
MOS_MIGRATED_REVID=106415882
|
|
This makes Android builds slightly faster and avoids the "Modification date is in the future" warnings by javac and removes the sources of devtools/common/options from the binary.
incrementaldeployment is not pre-compiled yet.
--
MOS_MIGRATED_REVID=106391321
|