New to bazel, so please excuse me for this basic question. I have a bazel extension file (repository.bzl) which provides a function to load all build dependencies (grpc as one of them) for my application as below: def load_depedencies(): maybe( http_archive, name: "com_github_grpc_grpc", urls: […], ) maybe (…) maybe (…) And this is loaded through ..
Currently, I try to build a library with Bazel (4.1.0) that originally uses CMake as a build system. I am running into a problem when trying to include a generated a header file using a relative path (in the CMake build it uses configure_file): WORKSPACE.bazel: workspace(name = "TemplateRule") main.cpp: #include "kernel/some_header.h" #include <iostream> int main() ..
I’ve been reading through the documentation for Building with platforms and Configuring C++ toolchains, and I am unable to clearly understand the best practice for defining compiler toolchains based upon the provided cc_tools autodetection (I just want to modify it). I have the following project directory tree (source files omitted): . ├── MyLib │ ├── ..
I want to use Templatized Command line arguements parser for c++ code using bazel, but quite unsure how to link the repository to bazel and use it in program. Can someone help me with this ? https://github.com/mirror/tclap/ Source: Windows Que..
I am attempting compiling the latest version of the Poco C++ libraries with bazel. I believe what is needed is a rules file describing in bazel terms how to compile the library. Has anyone attempted building one of these rules files? Source: Windows Que..