| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Makes some tests fail, oddly enough.
*** Original change description ***
Fixes to use dylib on MacOS X.
The change in LinkCommandLine.java fixes the error "ld: library not found for -ltbb.dylib". The change in osx_gcc_wrapper.sh fixes the error "dyld: Library not loaded: @rpath/libtbb.dylib".
See https://groups.google.com/forum/#!topic/bazel-discuss/bs8BnXYRjzY
--
MOS_MIGRATED_REVID=101012689
|
|
|
|
|
|
|
|
|
|
|
| |
The change in LinkCommandLine.java fixes the error "ld: library not found for -ltbb.dylib". The change in osx_gcc_wrapper.sh fixes the error "dyld: Library not loaded: @rpath/libtbb.dylib".
See https://groups.google.com/forum/#!topic/bazel-discuss/bs8BnXYRjzY
--
Change-Id: I7feb02eee7d059d86a6d29af391dc2fc71e1d0cc
Reviewed-on: https://bazel-review.googlesource.com/#/c/1831/
MOS_MIGRATED_REVID=101007071
|
|
|
|
|
|
|
| |
--
Change-Id: Ia70ca1b8482e10bc1ac91799aa238f8613e5c824
Reviewed-on: https://bazel-review.googlesource.com/#/c/1801
MOS_MIGRATED_REVID=100476467
|
|
|
|
|
|
|
|
|
| |
Also tweak the Android NDK CROSSTOOL file a bit so that it actually works.
Fixes #335.
--
MOS_MIGRATED_REVID=99377509
|
|
|
|
|
|
|
|
|
| |
Change CcLibrary to work both with and without declared outputs.
This fixed #61 - header-only libraries now compile on MacOS.
--
MOS_MIGRATED_REVID=99007746
|
|
|
|
|
|
|
|
|
| |
Fixes #99.
--
Change-Id: I9b81be7f8efc7f7e57b458fe91cfbabcaaee419d
Reviewed-on: https://bazel-review.googlesource.com/#/c/1632
MOS_MIGRATED_REVID=98472498
|
|
|
|
|
|
|
|
|
| |
running system.
Tested on OS X 10.10, Debian 8.1 (x86_64) and Debian 8.1 (i686).
--
MOS_MIGRATED_REVID=95819163
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=95506560
|
|
|
|
|
|
|
|
|
| |
Fixes #67
--
Change-Id: I0d52bcf6f8d5011af545e3d861914fae09a26e42
Reviewed-on: https://bazel-review.googlesource.com/1340
MOS_MIGRATED_REVID=93713804
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to my Mac, this is the search path:
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
#include "..." search starts here:
#include <...> search starts here:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1
/usr/local/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/clang/6.0/include
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include
/usr/include
/System/Library/Frameworks (framework directory)
/Library/Frameworks (framework directory)
Fixes #85.
--
MOS_MIGRATED_REVID=91194177
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=90612869
|
|
|
|
|
|
|
|
|
|
|
| |
Relative to the last try, add -B to Linux CROSSTOOL entry, and test
the result on OSX and Linux.
This should fix working with GCC cross compilers installed into
/usr/bin/ next to the host ld.
--
MOS_MIGRATED_REVID=90605463
|
|
|
|
|
|
|
|
|
|
|
| |
OS X does not have rpath so binary fails when not executing
from the good path. This wrapper rewrite the path after the
compilation to fix that behavior.
Fixes #46
--
MOS_MIGRATED_REVID=89527942
|
|
|
|
|
|
|
| |
Fixes #51
--
MOS_MIGRATED_REVID=89487705
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
This should remove the needs for the --cpu=darwin flag under darwin. Bazel build are now using the host cpu too.
This commit also fix the host cpu detection. The host cpu detection was too late and and some corner case was not really working with configurable attributes. It is now done as the default value for the --host_cpu flag.
--
MOS_MIGRATED_REVID=88427551
|
|
While attempting to clean up the Bazel examples, I noticed that the example
tests don't actually work because they expect a third_party directory. We could
link third_party/ from the top-level bazel directory, but then we'd have
crossing symlinks (base_workspace/tools->tools and
third_party->base_workspace/third_party). Linking everything in one direction
seemed like a better option, but alternative suggestions are welcome.
--
MOS_MIGRATED_REVID=86703332
|