aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools
Commit message (Collapse)AuthorAge
...
* Parse /showIncludes output for MSVC compilerGravatar Yun Peng2017-04-25
| | | | | | | | Instead of parsing .d file generated by wrapper script, we directly parse the output of /showIncludes option. Change-Id: Id94e20a5cb05a494a793fd6a43756d44d27cea8a PiperOrigin-RevId: 154161939
* Introduce the osx bazel crosstool template, with placeholder for ↵Gravatar cparsons2017-04-25
| | | | | | | cxx_builtin_include_directory. RELNOTES: None. PiperOrigin-RevId: 154094961
* Update to javac9-r4023Gravatar cushon2017-04-25
| | | | PiperOrigin-RevId: 154078281
* Clean up more things in MSVC wrapper scriptsGravatar Yun Peng2017-04-24
| | | | | | | | | | | 1. Moved /nologo flag into feature 2. No need to specify -m64, adding /MACHINVE:X64 as linker flag 3. Still use wrapper script to add /MT or /MD for now, because our users are depending on it: https://github.com/bazelbuild/bazel/issues/2120 We need a plan first before move them into CROSSTOOL Change-Id: If5e4c01a900fcf9e93877e04a893879897bff3a3 PiperOrigin-RevId: 154036870
* MSVC: attempt to choose msvcrt.lib vs libcmt.lib correctlyGravatar Steven Johnson2017-04-24
| | | | | | | | | See Issue #2120: if we specify /MD for copts, we should attempt to use MSVCRTx.lib instead of LIBCMTx.lib. Closes #2862. PiperOrigin-RevId: 154032031
* Add possibility to set ownership of files on pkg_tarGravatar Damien Martin-Guillerez2017-04-24
| | | | | Change-Id: Ic8c57c0ce78b5875135d5d1f19629ee40fd8f5f2 PiperOrigin-RevId: 153718869
* Support top level package for docker image.Gravatar Linuxer Wang2017-04-24
| | | | | | | | Fixes #616. Closes #2807. PiperOrigin-RevId: 153714590
* Remove tools/build_defs/apple/apple.bzl.Gravatar thomasvl2017-04-20
| | | | PiperOrigin-RevId: 153589856
* Add missing dependency.Gravatar Googler2017-04-20
| | | | PiperOrigin-RevId: 153584278
* Move the sha256 tool into its own directory, as it isn't specific to ↵Gravatar Googler2017-04-19
| | | | | | docker_build. PiperOrigin-RevId: 153508081
* Automated g4 rollback of commit 501b62716af12ba42c019bd9f231468b3c144757.Gravatar aehlig2017-04-18
| | | | | | | | | | | | | | | *** Reason for rollback *** Broke //src/test/shell/bazel:cc_inc_library_test on darwin see http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD,PLATFORM_NAME=darwin-x86_64/704/console *** Original change description *** Basic open-source crosstool to support targetting apple platform types. RELNOTES: None. PiperOrigin-RevId: 153460334
* Generating PDB files on WindowsGravatar Yun Peng2017-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | 1. Add /Z7 as compiler flag in CROSSTOOL, this causes full debugging infomation built into object files, no PDB file is generated. 2. Add /DEBUG as linker flag so that a PDB file will be generated for executable or dll. * /DEBUG:FULL for dbg mode. the full PDB can be used to debug the executable when no other build products are available, such as when the executable is deployed. * /DEBUG:FASTLINK for fastbuild mode. object files are still needed when debugging the executable, but linking speed can be two to four times faster that full PDB generation. * No option is added for opt mode. More detailed info: https://msdn.microsoft.com/en-us/library/xe4t6fc1.aspx 3. Add an empty feature in MSVC CROSSTOOL to tell Bazel we need PDB file 4. Add PDB file artifact in an output named pdb_file of cc_binary, then you can build the pdb file by bazel build //foo/bar:bin --output_groups=pdb_file 5. Add test for PDB file generation Change-Id: Ia5096470187ebca72f2c804f32d5b723f40c0b85 PiperOrigin-RevId: 153449059
* Basic open-source crosstool to support targetting apple platform types.Gravatar cparsons2017-04-18
| | | | | RELNOTES: None. PiperOrigin-RevId: 153360877
* Expose Bazel's Android data binding support to users.Gravatar gregce2017-04-18
| | | | | | | | | | | | The logic is already in Bazel but wasn't available to build rules. This change makes it available, but still requires data binding's {build|run}time libraries to be checked into appropriate depot spots for everything to work. Followup changes will make those libraries easily available. Issue: #2694 PiperOrigin-RevId: 153359861
* Automated g4 rollback of commit 045104899738594d85f9ab9b0b9ccbde320b8055.Gravatar jfield2017-04-18
| | | | | | | | | | | | | *** Reason for rollback *** Breaks internal tests that use nonstandard crosstools *** Original change description *** Make C++ archiving use action_configs instead of hardcoded flags RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag. PiperOrigin-RevId: 153344597
* Move xcrunwrapper and libtool to third_party/bazel/tools/objc from their ↵Gravatar cparsons2017-04-14
| | | | | | | | | xcode src directories There's no value in having these copied over from src/tools to tools/objc separately. RELNOTES: None. PiperOrigin-RevId: 153060955
* Make C++ archiving use action_configs instead of hardcoded flagsGravatar hlopko2017-04-13
| | | | | RELNOTES: Use action_config in crosstool for static library archiving, remove ar_flag. PiperOrigin-RevId: 153046587
* Do not add a build id to C++ binaries by default.Gravatar lberki2017-04-13
| | | | | | | Fixes #2805. RELNOTES: None. PiperOrigin-RevId: 153039178
* Aspect-side compatibility with pending external workspace changes.Gravatar Googler2017-04-13
| | | | PiperOrigin-RevId: 152979269
* Make android_sdk_repository generate filegroups containing system image ↵Gravatar ajmichael2017-04-12
| | | | | | | | | | | | | | | | | | files for all android system images installed in the SDK. For system images that are not installed, create genrule "poison pills" that print a helpful error message if you attempt to build them. These filegroups are intended to be used as the system_image attribute of the android_device rule. Example: $ bazel build @android_test_support//tools/android/emulated_devices/pixel:android_25_x86 Extracting Bazel installation... . INFO: Found 1 target... ERROR: /usr/local/google/home/ajmichael/.cache/bazel/_bazel_ajmichael/efa32264346ef1fc4fec492202b88b31/external/androidsdk/BUILD.bazel:56:1: Executing genrule @androidsdk//:emulator_images_android_25_x86 failed: Process exited with status 1 [sandboxed]. This rule requires that the Android SDK used by Bazel has the following system image installed: emulator_images_android_25_x86. Please install this system image through the Android SDK Manager and try again. RELNOTES: None PiperOrigin-RevId: 152889824
* Copy swift.bzl into bazel_rules/rules_apple.Gravatar allevato2017-04-11
| | | | PiperOrigin-RevId: 152729637
* Add toolchain_rule to enable rule authors to define toolchains.Gravatar John Cater2017-04-11
| | | | | Change-Id: I407240708f4aacc89ec5c00bf3e8ff46a1d6d6d6 PiperOrigin-RevId: 152692981
* Use sha256 prefix when tagging docker images with full IDsGravatar Jason Young2017-04-11
| | | | | | | | | | | | | | | | | | | | Newer versions of docker require 'sha256' prefix with full IDs (see https://github.com/docker/docker/issues/20972#issuecomment-193381422). Without the prefix users get the following error with newer versions of docke, e.g. 17.04.0-ce-rc1: $ docker tag 7cd4bfeb6766d1c5e5d729b7444cba3d9f97dfddfbeab90ed2e3f7147804ee8f \ docker.io/<user>/<image>:<tag> Error parsing reference: "7cd4bfeb6766d1c5e5d729b7444cba3d9f97dfddfbeab90ed2e3f7147804ee8f" is not a valid repository/tag: invalid repository name (7cd4bfeb6766d1c5e5d729b7444cba3d9f97dfddfbeab90ed2e3f7147804ee8f), cannot specify 64-byte hexadecimal strings --- I'm not sure if this is the proper solution, but it seems to fix the problem with docker version `17.04.0-ce-rc1` as well as older docker version (e.g. `1.12.0`). Alternative solutions welcome. Closes #2755. PiperOrigin-RevId: 152685896
* cc_configure: stricter error checks in _executeGravatar laszlocsomor2017-04-11
| | | | | | | | | | | | | | | | | Add stricter error checks in hopes of catching occasional CI flakiness where the stdout of a command seems to get lost. It's now an error if the command returns a non-zero exit code (or a zero one if it's expected to fail) or if its stdout is empty. Previously we only checked if stderr was empty to consider the action successful. See https://github.com/bazelbuild/bazel/issues/2675 RELNOTES: none PiperOrigin-RevId: 152685220
* Provide more information regarding compilerGravatar Eric Cousineau2017-04-10
| | | | | | | | | | | | | | | | | | | | This addresses #2761, to provide a minor improvement if neither `gcc` or `CC` are found on the path. Let me know if you would like anything changed! Local qualification steps: ``` $ cd bazel $ git rebase 0.4.5 # Did not want to spend too much time synchronizing derived stuff in master $ ln -s ~/Downloads/bazel-0.4.5-dist/derived . $ ./compile.sh $ export PATH=~+/output/bazel;$PATH $ cd .../someproject $ CC=clang-9000 bazel build //package:test Cannot find gcc or CC (clang-9000), either correct your path or set the CC environment variable. ``` Closes #2773. PiperOrigin-RevId: 152658002
* Suppress some warning messages from cc_configure.bzlGravatar Yun Peng2017-04-06
| | | | | | | Fixed https://github.com/bazelbuild/bazel/issues/2775 Change-Id: I4f5bab56ab961fd5310d62c7eee70abf9c98f9d9 PiperOrigin-RevId: 152359801
* Remove apkbuilder from Bazel's android_sdk.Gravatar ajmichael2017-04-06
| | | | | | RELNOTES: None PiperOrigin-RevId: 152292294
* Windows MSVC toolchain: Move environment variables setup from wrapper script ↵Gravatar Yun Peng2017-04-06
| | | | | | | to CROSSTOOL Change-Id: Ic6ee5a22412281743267a40623f4a8514a2e70f6 PiperOrigin-RevId: 152252048
* Small shell fixed to cleanup distfile testingGravatar Stephen Twigg2017-04-05
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fix permissions issue in testenv.sh to clarified chmod on tools/jdk/BUILD when copying tools into new workspace: Original script always tried to append but only set it to be writable after the copy when extra BUILD.* files were available. Exported is_absolute in test-setup.sh: rlocation, which is called by tests to properly locate bazel, itself calls is_absolute. This would generally cause a (presumably recoverable) error since most tests continue to call a bazel properly. However, tests that are inspecting the error log will fail due to the message error. Note, that not all tests pass yet. Also getting an issue with: * scripts/release/testenv.sh : line 38 (file doesn't exist) * in test_delete_tree_in_unwritable_dir, "fails on first compilation: due to mkdir: cannot create directory 'bazel-out/local-fastbuild/genfiles/x/unwritable/somedir' * test_run_under_path 'occasionally' fails to fail (bazel_test_test.sh:197) Change-Id: I957a346d320070a310dee4076cc9349ed1e140e1 PiperOrigin-RevId: 152247475
* Remove jack tools from Bazel.Gravatar ajmichael2017-04-05
| | | | | | | | #1391 RELNOTES: None PiperOrigin-RevId: 152179305
* adding more env vars to invalidation listGravatar Nicolas Lopez2017-04-04
| | | | | | | | | It seems several env vars that are used by cc_configure are not in the invalidation list and not included in the bootstrap compile. Adding them. Change-Id: I67f73ae09abbe9033bcbbcb4026dab04d225b699 PiperOrigin-RevId: 152139948
* Disable cc_configure tests on debian stretch altogetherGravatar hlopko2017-04-04
| | | | | | | | | | | | | Not only opt builds fail, also fastbuild: http://ci.bazel.io/view/Dashboard/job/bazel-docker-tests/lastCompletedBuild/BAZEL_VERSION=latest,PLATFORM_NAME=docker/console The issue is tracked here: https://github.com/bazelbuild/bazel/issues/2418 RELNOTES: NONE. PiperOrigin-RevId: 152109844
* Scan both .h and .m files for imports and includesGravatar Googler2017-04-04
| | | | | | | | The dependency mappings are generated by scanning the .m files. I found a case where a header file was only imported in the .h file. RELNOTES: None. PiperOrigin-RevId: 152050144
* Roll forward change https://cr.bazel.build/9250 with Java 7 build failure fix.Gravatar xingao2017-04-04
| | | | | | | | | Make Java tool jars available from @bazel_tools. Now users can point to default Java tool jars in customized java_toolchain rule defined in project's BUILD file. PiperOrigin-RevId: 152012191
* Add internal section to override android jar.Gravatar Googler2017-04-03
| | | | PiperOrigin-RevId: 151825956
* Fix MSVC CROSSTOOL for linking against lib filesGravatar pcloudy2017-03-31
| | | | | | | | | | | | | | | | 1. No need to add /WHOLEARCHIVE option for object files 2. When linking against a .lib file of a dll with /WHOLEARCHIVE option, the linker produces an error. So strip it in msvc_link.py. The second point is a temporary workaround to make TF GPU build work, we'll fix it properly when we figure out how to deal with .lib, .dll, .pdb files on Windwos. Fix https://github.com/bazelbuild/bazel/issues/2753 Change-Id: Ia77b67546bfd4f19ceeb0f6ab9ab3b7a598c4fe9 PiperOrigin-RevId: 151811504
* Bazel, Windows: can now test cc_test rules : Windows: bazel test now works ↵Gravatar laszlocsomor2017-03-31
| | | | | | | | for cc_test rules Change-Id: I0983793edd1a5ca281fbb8f8a100e792381b0ff4 PiperOrigin-RevId: 151708025
* Automated g4 rollback of commit 99a5a30d17d920de323d1cc37e3fe25a0749ae41.Gravatar philwo2017-03-31
| | | | | | | | | | | | | | | | | | *** Reason for rollback *** Breaks Java 7 tests: ERROR: missing input file '@bazel_tools//tools/jdk:JavaBuilder_deploy.jar' http://ci.bazel.io/job/bazel-tests/BAZEL_VERSION=HEAD-jdk7,PLATFORM_NAME=linux-x86_64/670/console *** Original change description *** Make Java tool jars available from @bazel_tools. Now users can point to default Java tool jars in custmized java_toolchain rule defined in project's BUILD file. PiperOrigin-RevId: 151699090
* Docker tests: deactivate Ubuntu 15.10 and Debian stretch optGravatar dmarting2017-03-29
| | | | | | | - Ubuntu 15.10 has passed end of life - Debian stretch is flaky with optimized build (see #2418) PiperOrigin-RevId: 151567467
* Make Java tool jars available from @bazel_tools. Gravatar Xin Gao2017-03-28
| | | | | | | | | | | Now users can point to default Java tool jars in custmized java_toolchain rule defined in project's BUILD file. -- Change-Id: I064c9646e8681a3f5669d7163b1b3cb5cc0b16b7 Reviewed-on: https://cr.bazel.build/9250 PiperOrigin-RevId: 151422924 MOS_MIGRATED_REVID=151422924
* Replacing hardcoded use of 'local' for env variables in cc autoconfigGravatar Nicolas Lopez2017-03-28
| | | | | | | | -- Change-Id: Ic1632229e67bf82b69983f9614258c5fd54c12d8 Reviewed-on: https://cr.bazel.build/9390 PiperOrigin-RevId: 151422502 MOS_MIGRATED_REVID=151422502
* Don't filter out warning messages from MSVC python wrappers anymore.Gravatar Yun Peng2017-03-28
| | | | | | | | | | | Fixed: https://github.com/bazelbuild/bazel/issues/2666 See: https://github.com/bazelbuild/bazel/issues/2726 RELNOTES: Windows MSVC wrappers: Not filtering warning messages anymore, use --copt=-w and --host_copt=-w to suppress them. -- PiperOrigin-RevId: 151422047 MOS_MIGRATED_REVID=151422047
* Add test for ubuntu 16.04Gravatar Damien Martin-Guillerez2017-03-27
| | | | | | | | | | This only add the bootstrap tests. We could add more tests but we should probably rather just update the 15.10 VMs to run Ubuntu 16.04. Tracking issue #2741. -- PiperOrigin-RevId: 151299465 MOS_MIGRATED_REVID=151299465
* Description redacted.Gravatar Googler2017-03-27
| | | | | | -- PiperOrigin-RevId: 151263526 MOS_MIGRATED_REVID=151263526
* Disable sandboxing for some bundling actions.Gravatar Googler2017-03-27
| | | | | | -- PiperOrigin-RevId: 151193034 MOS_MIGRATED_REVID=151193034
* Add "resources", "structured_resources" attrs to swift_library.Gravatar Googler2017-03-27
| | | | | | -- PiperOrigin-RevId: 151183770 MOS_MIGRATED_REVID=151183770
* Add a script to generate the Java-class-to-objc-header mapping for J2ObjC. ↵Gravatar Rumou Duan2017-03-27
| | | | | | | | | | Previously the mapping is generated directly by J2ObjC through j2objc_wrapper.py. RELNOTES:None. -- PiperOrigin-RevId: 151138711 MOS_MIGRATED_REVID=151138711
* Rollback of commit 701ff40ad9d1b6c1e3beb52064e2ae2fe27b7e29.Gravatar Dmitry Shevchenko2017-03-24
| | | | | | | | | | | | | | | | | | *** Reason for rollback *** No longer needed, as the original tool was re-introduced in Xcode 8.3 beta 5 *** Original change description *** Introduce swift-stdlib-tool replacement * swift-stdlib-tool is a utility that, given a binary, walks its dynamic library deps graph and picks everything that is used by Swift runtime. This tool is being removed from Xcode 8.3, hence the replacement. * The new tool has a different command line interface, but keeps backwards compatibility with native Bazel code through changes in the wrapper script. The wrapper script is still needed to handle xcrun ENV stuff. -- PiperOrigin-RevId: 151052031 MOS_MIGRATED_REVID=151052031
* Add default constraint_settings and values in new package ↵Gravatar John Cater2017-03-23
| | | | | | | | | | | | @bazel_tools//platforms. Part of #2219. -- Change-Id: I312c70e0c9064cbf4c4346a59bff04ada92e4890 Reviewed-on: https://cr.bazel.build/9412 PiperOrigin-RevId: 151016060 MOS_MIGRATED_REVID=151016060
* cc_configure: more generic msys_root discovery Gravatar László Csomor2017-03-23
| | | | | | | | | | | See https://github.com/bazelbuild/bazel/issues/2725 Related to https://github.com/bazelbuild/bazel/issues/2447 -- Change-Id: I5cc7fba43ae46bc9ef47bcaf9efaf2a0b9911bc4 Reviewed-on: https://cr.bazel.build/9468 PiperOrigin-RevId: 150881196 MOS_MIGRATED_REVID=150881196
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-19 11:41:56 +0000