Log - refs/tags/rel/13/fp3/6.A.022.1 - platform/external/google-fruit

c6d389d Fix bazel build errors introduced by 94cefefb42f3685c1d64664e6aa9cbaf834b25ee when the Fruit headers are not also installed on the system where bazel runs. by Marco Poletti · 3 years, 10 months ago
94cefef Automatically detect compiler features when running under Bazel. Before this commit, bazel builds used a hardcoded configuration, but that doesn't work e.g. on Windows where MSVC needs a different config. by Marco Poletti · 3 years, 10 months ago
faa6922 Declare the dep on boost in bazel, so that Fruit builds even on systems where Boost isn't installed. This required some refactoring of the testing code, since we can't depend on the Boost headers as a fileset (that we'd need) so generated code in tests can't include Boost anymore. by Marco Poletti · 4 years ago
6df80a7 Use extras/bazel_root as WORKSPACE root for Bazel, using symlinks so that Fruit lives under //third_party/fruit instead of //. by Marco Poletti · 8 years ago
78e1e53 Add an explicit "-lm" linker flag when building with Bazel, this seems to be needed now for some reason (and it's currently causing the build failure with Bazel in Travis CI). by Marco Poletti · 8 years ago
18fb995 Support Bazel as an alternative build system (in parallel with CMake). by Marco Poletti · 8 years ago
c8ecca8 Add draft BUILD files for the Bazel build system. Building with Bazel currently doesn't work, it results in this compile error: by Marco Poletti · 8 years ago