bazel | a fast , scalable , multi-language and extensible build system | Build Tool library

by bazelbuild Java Version: 7.0.0-pre.20230118.2 License: Apache-2.0

kandi X-RAY | bazel Summary

bazel is a Java library typically used in Utilities, Build Tool applications. bazel has a Permissive License and it has high support. However bazel has 3137 bugs, it has 19 vulnerabilities and it build file is not available. You can download it from GitHub.

Build and test software of any size, quickly and reliably.

Support

Quality

Security

License

Reuse

kandi-support Support

bazel has a highly active ecosystem.
It has 20194 star(s) with 3659 fork(s). There are 612 watchers for this library.
There were 10 major release(s) in the last 6 months.
There are 2419 open issues and 8312 have been closed. On average issues are closed in 975 days. There are 167 open pull requests and 0 closed requests.
It has a negative sentiment in the developer community.
The latest version of bazel is 7.0.0-pre.20230118.2

bazel Support

Best in #Build Tool

Average in #Build Tool

bazel Support

Best in #Build Tool

Average in #Build Tool

quality kandi Quality

bazel has 3137 bugs (105 blocker, 12 critical, 1358 major, 1662 minor) and 34552 code smells.

bazel Quality

Best in #Build Tool

Average in #Build Tool

bazel Quality

Best in #Build Tool

Average in #Build Tool

security Security

bazel has 2 vulnerability issues reported (0 critical, 1 high, 1 medium, 0 low).
bazel code analysis shows 17 unresolved vulnerabilities (16 blocker, 1 critical, 0 major, 0 minor).
There are 311 security hotspots that need review.

bazel Security

Best in #Build Tool

Average in #Build Tool

bazel Security

Best in #Build Tool

Average in #Build Tool

license License

bazel is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

bazel License

Best in #Build Tool

Average in #Build Tool

bazel License

Best in #Build Tool

Average in #Build Tool

build Reuse

bazel releases are available to install and integrate.
bazel has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions are available. Examples and code snippets are not available.
bazel saves you 2068197 person hours of effort in developing the same functionality from scratch.
It has 847515 lines of code, 63294 functions and 6202 files.
It has medium code complexity. Code complexity directly impacts maintainability of the code.

bazel Reuse

Best in #Build Tool

Average in #Build Tool

bazel Reuse

Best in #Build Tool

Average in #Build Tool

Top functions reviewed by kandi - BETA

kandi has reviewed bazel and discovered the below as its top functions. This is intended to give you an instant insight into bazel implemented functionality, and help decide if they suit your requirements.

Add legacy features .

Execute the given command and return the result .

Creates a new target .

The binary operator .

Parse the member specification arguments .

Evaluate a single instruction block .

Visit an instruction .

Visit a program class .

Configures the skyframe execution .

Search for cycles .

Get all kandi verified functions for this library.

bazel Key Features

Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.

One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.

Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.

Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.

bazel Examples and Code Snippets

See all related Code Snippets

Community Discussions

Trending Discussions on bazel

Build from source error: missing input file 'external/net_sf_jchart2d/jar/jchart2d.jar'
Build and run a Qt application on macOS via Bazel
How to build header only C++ library within Bazel workspace?
Bazel: how to import/build a go_binary for a go_test
Use bazel library inside cmake project
Bazel build docker container with local golang module
Using Rules Foreign CC to Build AWS C++ SDK with Bazel
How to find logs from bazel's previous runs
Golang: fatal error: unexpected signal during runtime execution
How to do configuration and variant handling in Bazel?

Trending Discussions on bazel

QUESTION

Build from source error: missing input file 'external/net_sf_jchart2d/jar/jchart2d.jar'

Asked 2022-Mar-05 at 15:32

I try to build drake1.0.0 from source using bazel. However I encounter the following error:

ERROR: /home/chenwang/drake-build/_bazel_chenwang/bcff9e14963ec4b6ed21d9b7e9e180fc/external/net_sf_jchart2d/jar/BUILD.bazel:2:12: Extracting interface @net_sf_jchart2d//jar:jar failed: missing input file 'external/net_sf_jchart2d/jar/jchart2d.jar', owner: '@net_sf_jchart2d//jar:jchart2d.jar'
ERROR: /home/chenwang/drake-build/_bazel_chenwang/bcff9e14963ec4b6ed21d9b7e9e180fc/external/net_sf_jchart2d/jar/BUILD.bazel:2:12: Extracting interface @net_sf_jchart2d//jar:jar failed: 1 input file(s) do not exist
Target //:install failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /home/chenwang/drake-build/_bazel_chenwang/bcff9e14963ec4b6ed21d9b7e9e180fc/external/net_sf_jchart2d/jar/BUILD.bazel:2:12 Extracting interface @net_sf_jchart2d//jar:jar failed: 1 input file(s) do not exist
INFO: Elapsed time: 23.087s, Critical Path: 8.22s
INFO: 2890 processes: 2584 internal, 306 linux-sandbox.
FAILED: Build did NOT complete successfully
CMakeFiles/drake_cxx_python.dir/build.make:110: recipe for target 'drake_cxx_python-prefix/src/drake_cxx_python-stamp/drake_cxx_python-build' failed
make[2]: *** [drake_cxx_python-prefix/src/drake_cxx_python-stamp/drake_cxx_python-build] Error 1
CMakeFiles/Makefile2:931: recipe for target 'CMakeFiles/drake_cxx_python.dir/all' failed
make[1]: *** [CMakeFiles/drake_cxx_python.dir/all] Error 2
Makefile:162: recipe for target 'all' failed
make: *** [all] Error 2

I have built older version drake from source successfully. It seems that I miss some third-party library for building the new version drake. Thank you for your help!

ANSWER

Answered 2022-Mar-05 at 15:32

It turns out that the install_repreqs.sh has been updated and I forget to rerun it. After installing the prerequisite by rerunning install_repreqs.sh, I can build drake from source successfully.

Source https://stackoverflow.com/questions/71362872

QUESTION

Build and run a Qt application on macOS via Bazel

Asked 2022-Feb-16 at 17:13

I tried to build and run a Qt5 (5.15.2) application on macOS (10.15.7) using Bazel 5.0.0. Unfortunately, I run into some problems. The building part seems to work, but not the run part.

I installed Qt5 on my machine using Homebrew:

brew install qt@5
brew link qt@5

I adapted https://github.com/justbuchanan/bazel_rules_qt/ to my needs. See this PR. When I try to run:

bazel run --cxxopt=-std=c++17 //tests/qt_resource:main

I receive the runtime error:

dyld: Symbol not found: __ZN10QByteArray6_emptyE

Steps to reproduce the issue:

# brew install bazel # Install Bazel
# brew install qt@5  # Install Qt5
git clone https://github.com/Vertexwahn/bazel_rules_qt.git
cd bazel_rules_qt
git checkout add-macos-support
bazel build --cxxopt=-std=c++17 //... # should work
bazel run --cxxopt=-std=c++17 //tests/qt_resource:main # should give you the error message

Nevertheless, building everything using bazel build --cxxopt=-std=c++17 //... seems to work. I am not 100% sure if the link options -F/usr/local/opt/qt5/Frameworks and -framework QtCore, etc. are correct. Maybe someone can confirm this.

Did I use the correct link options?

For me, it is a bit unclear what dependencies the main binary expects. I tried to copy QtCore.framework to the location of the main binary manually but this does not change the error message.

What files does the main binary expect?

If I try to run macdeployqt on my main binary I get also some errors. I do within my workspace root dir a cd bazel-bin/tests/qt_resource and run then /usr/local/opt/qt5/bin/macdeployqt main:

ERROR: Could not find bundle binary for "main"
ERROR: "error: /Library/Developer/CommandLineTools/usr/bin/otool-classic: can't open file:  (No such file or directory)\n"
ERROR: "error: /Library/Developer/CommandLineTools/usr/bin/otool-classic: can't open file:  (No such file or directory)\n"
ERROR: "error: /Library/Developer/CommandLineTools/usr/bin/otool-classic: can't open file:  (No such file or directory)\n"
WARNING:
WARNING: Could not find any external Qt frameworks to deploy in "main"
WARNING: Perhaps macdeployqt was already used on "main" ?
WARNING: If so, you will need to rebuild "main" before trying again.
ERROR: Could not find bundle binary for "main"
ERROR: "error: /Library/Developer/CommandLineTools/usr/bin/strip: can't open file:  (No such file or directory)\n"
ERROR: ""

My hope was that macdeployqt would collect all needed resources for me. Any idea why this is not working?

How can macdeployqt be used to collect all needed dependencies for the main binary?

If I convert my main to an app via lipo -create -output universall_app main and do then a /usr/local/opt/qt5/bin/macdeployqt universall_app I get the same error message.

The CMake approach

To make sure that there is no general problem with my system setup I tried to use CMake to build a Qt5 application:

git clone https://github.com/euler0/mini-cmake-qt.git
cmake -DCMAKE_PREFIX_PATH=/usr/local/opt/qt5 .
make -j

This produces an example.app. With a double click on this application bundle, the application can be started. This worked on my system.

Future directions

It seems that rules_apple can be used to create an application bundle. I am not sure if I need to transform my Qt application binary to an app bundle to be able to execute it. One could use --sandbox_debugto identify what Bazel is doing and dtruss for the CMake version to compare the differences. I am currently not sure what trying to do next and hope for an easy solution. I am also fine with a Qt6 solution.

Update: Alternative Answer

It would also be helpful if someone can point out how to build a minimal Qt application using make only on macOS and a brew installed Qt5 or tell me what the linker and compiler options must look like.

ANSWER

Answered 2022-Feb-16 at 17:13

I followed your steps with Mac OSX 10.15.7, Qt (installed by homebrew) 5.15.1 and both bazel 4.2.2-homebrew and 5.0.0-homebrew and initially I could not build the project from git:

* 3fe5f6c - (4 weeks ago) Add macOS support — Vertexwahn (HEAD -> add-macos-support, origin/add-macos-support)

This is the result that I get when building:

 % bazel build --cxxopt=-std=c++17  //...
 DEBUG: /private/var/tmp/_bazel_home/761aafaa2237a9607dd915f1f52bca3e/external/com_justbuchanan_rules_qt/qt_configure.bzl:43:14: Installation available on the default path:  /usr/local/opt/qt5
 INFO: Analyzed 14 targets (0 packages loaded, 0 targets configured).
 INFO: Found 14 targets...
 ERROR: /Users/home/Git/my_repo/bazel_rules_qt/tests/qt_qml/BUILD:4:10: Compiling tests/qt_qml/main.cc failed: (Aborted): wrapped_clang failed: error executing command external/local_config_cc/wrapped_clang '-D_FORTIFY_SOURCE=1' -fstack-protector -fcolor-diagnostics -Wall -Wthread-safety -Wself-assign -fno-omit-frame-pointer -O0 -DDEBUG '-std=c++11' ... (remaining 38 argument(s) skipped)

 Use --sandbox_debug to see verbose messages from the sandbox
 tests/qt_qml/main.cc:1:10: fatal error: 'QtQml/QQmlApplicationEngine' file not found
 #include <QtQml/QQmlApplicationEngine>
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 1 error generated.
 Error in child process '/usr/bin/xcrun'. 1
 INFO: Elapsed time: 0,594s, Critical Path: 0,32s
 INFO: 3 processes: 3 internal.
 FAILED: Build did NOT complete successfully

After playing around with headers and include paths in qt.BUILD:

 diff --git a/qt.BUILD b/qt.BUILD
 index 517c8db..8f110b5 100644
 --- a/qt.BUILD
 +++ b/qt.BUILD
 @@ -28,11 +28,12 @@ QT_LIBRARIES = [
      cc_library(
          name = "qt_%s_osx" % name,
          # When being on Windows this glob will be empty
 -        hdrs = glob(["%s/**" % include_folder], allow_empty = True),
 +        hdrs = glob(["include/%s/**" % include_folder], allow_empty = True),
          includes = ["."],
          linkopts = ["-F/usr/local/opt/qt5/lib"] + [
              "-framework %s" % library_name.replace("5", "") # macOS qt libs do not contain a 5 - e.g. instead of Qt5Core the lib is called QtCore
              ],
 +        strip_include_prefix= "include"
          # Available from Bazel 4.0.0
          # target_compatible_with = ["@platforms//os:osx"],
      )

I could build and run the project:

 % bazel build --cxxopt=-std=c++17  //...
 DEBUG: /private/var/tmp/_bazel_home/761aafaa2237a9607dd915f1f52bca3e/external/com_justbuchanan_rules_qt/qt_configure.bzl:43:14: Installation available on the default path:  /usr/local/opt/qt5
 INFO: Analyzed 14 targets (1 packages loaded, 7422 targets configured).
 INFO: Found 14 targets...
 INFO: Elapsed time: 11,761s, Critical Path: 7,23s
 INFO: 3 processes: 1 internal, 2 darwin-sandbox.
 INFO: Build completed successfully, 3 total actions
 % bazel run --cxxopt=-std=c++17 //tests/qt_resource:main
 DEBUG: /private/var/tmp/_bazel_home/761aafaa2237a9607dd915f1f52bca3e/external/com_justbuchanan_rules_qt/qt_configure.bzl:43:14: Installation available on the default path:  /usr/local/opt/qt5
 INFO: Analyzed target //tests/qt_resource:main (0 packages loaded, 0 targets configured).
 INFO: Found 1 target...
 Target //tests/qt_resource:main up-to-date:
 bazel-bin/tests/qt_resource/main
 INFO: Elapsed time: 3,657s, Critical Path: 0,00s
 INFO: 1 process: 1 internal.
 INFO: Build completed successfully, 1 total action
 INFO: Build completed successfully, 1 total action
 opened resource file
 file1

Related to your question whether the linker options are correct -F/usr/local/opt/qt5/Frameworks -framework QtCore

Yes they are correct, you could alternatively use -F/usr/local/opt/qt5/lib (as you are already using in qt.BUILD) as all the files under the Frameworks folder are links to the lib folder.

With macdeployqt and lipo I get the same results as in the OP even after the test is running successfully.

Source https://stackoverflow.com/questions/71040975

QUESTION

How to build header only C++ library within Bazel workspace?

Asked 2022-Feb-07 at 19:50

I'm working on a C++ project and I need Numpy like arrays and functionalities in C++. I found some alternatives like xtensor, NumCpp etc. These are header only libraries. The problem is I'm experimenting with Bazel for the first time so, I don't have any idea about how do I add header only library to Bazel workspace. There are some suggestions like genrule-environment, rules-foreign-cc suggested on other questions around Bazel. I've added http_archive to WORKSPACE file, but I'm not sure what to add in BUILD file.

WORKSPACE file

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

all_content = """filegroup(name = "all", srcs = glob(["**"]), visibility = ["//visibility:public"])"""

http_archive(
    name = "xtensor",
    build_file_content = all_content,
    strip_prefix = "xtensor-master",
    urls = ["https://github.com/xtensor-stack/xtensor/archive/refs/heads/master.zip"],
)

http_archive(
    name = "NumCpp",
    build_file_content = all_content,
    strip_prefix = "NumCpp-master",
    urls = ["https://github.com/dpilger26/NumCpp/archive/refs/heads/master.zip"],
)

http_archive(
    name = "rules_foreign_cc",
    sha256 = "c2cdcf55ffaf49366725639e45dedd449b8c3fe22b54e31625eb80ce3a240f1e",
    strip_prefix = "rules_foreign_cc-0.1.0",
    url = "https://github.com/bazelbuild/rules_foreign_cc/archive/0.1.0.zip",
)

load("@rules_foreign_cc//:workspace_definitions.bzl", "rules_foreign_cc_dependencies")

rules_foreign_cc_dependencies()

I've tried to follow documentation, but failed every time. Some help would be appreciated.

ANSWER

Answered 2022-Feb-07 at 19:50

For simple things like header-only libraries, I would write BUILD files yourself, without using rules_foreign_cc. Just write a cc_library with no srcs. Something like this:

http_archive(
    name = "xtensor",
    build_file_content = all_content,
    strip_prefix = "xtensor-master",
    urls = ["https://github.com/xtensor-stack/xtensor/archive/refs/heads/master.zip"],
    build_file_content = """
cc_library(
    name = "xtensor",
    visibility = ["//visibility:public"],
    hdrs = glob(["xtensor/*.hpp"]),
    defines = [
        "XTENSOR_ENABLE_ASSERT",
    ],
    deps = [
        "@tbb",
    ],
)
""",
)

@xtensor will be your Bazel repository. The build_file_content will be used to create a BUILD.bazel file in it. That means your code can depend on it via @xtensor//:xtensor, which can be shortened to just @xtensor. You can also put that in a separate file (say build/BUILD.xtensor.bazel) and then use build_file = "@build//:BUILD.xtensor.bazel" instead of putting it inline in WORKSPACE via build_file_content.

rules_foreign_cc is going to generate something equivalent if you get it set up, but that seems like a lot more trouble to me than just writing it yourself. I set defines and deps based on a scan through the CMakeLists.txt, you'll want to customize based on how you want it configured.

The only other thing I see that CMakeLists doing (beyond finding dependencies and setting some -D flags, which translate as shown above) is generating a single file that #includes all the others. If you want to do that, I'd do something like this (in the BUILD file for @xtensor):

genrule(
    name = "gen_single_include",
    outs = ["xtensor.hpp"],
    cmd = "\n".join([
        "cat > $@ <<'END'",
        "#ifndef XTENSOR",
        "#define XTENSOR",
    ] + ["#include \"%s\"" % h[len("xtensor/"):]
         for h in glob(["xtensor/*.hpp"])
         if h not in [
             "xtensor/xexpression_holder.hpp",
             "xtensor/xjson.hpp",
             "xtensor/xmime.hpp",
             "xtensor/xnpy.hpp",
          ]] + [
        "#endif",
        "END",
    ]),

I may not have gotten everything perfect here, but the idea is to build up the file using cat to copy stdin to it, a bash here document to feed the content in, and Python-style list comprehensions to actually build up the content.

Source https://stackoverflow.com/questions/71023144

QUESTION

Bazel: how to import/build a go_binary for a go_test

Asked 2022-Jan-24 at 20:06

I'm using bazel to run a go test on my CI system. The go test will need to use a helper binary built from another go file.

The dir structure looks like the following:


    some/of/my/path
    ├── BUILD.bazel
    ├── my_utils.go
    ├── my_test.go
    └── my_tool
        ├── BUILD.bazel
        └── my_tool.go

I.e. the code in my_test.go is going to use the executable binary built from dir my_tool.

In a non-bazel case, I can just go build ./mytool to get the executable binary that my_test.go needs. To accommodate this the bazel world, I write the following in the bazel files:

In some/of/my/path/BUILD.bazel:


    load("@io_bazel_rules_go//go:def.bzl", "go_library", "go_test")
    
    go_library(
        name = "testutils",
        srcs = ["my_utils.go"],
        importpath = "some/of/my/path",
        visibility = ["//visibility:public"],
        deps = [
            "@org_golang_x_net//context",
            ... (some other dependencies, not related)
        ],
    )
    
    go_test(
        name = "my_test",
        size = "enormous",
        srcs = ["mytest.go"],
        embed = [":testutils"],
        deps = [
            "//some/of/my/path/my_tool:my_tool",
        ],
    )

In some/of/my/path/my_tool/BUILD.bazel


    load("@io_bazel_rules_go//go:def.bzl", "go_binary", "go_library")
    
    go_library(
        name = "my_tool_lib",
        srcs = ["my_tool.go"],
        importpath = "some/of/my/path/my_tool",
        visibility = ["//visibility:private"],
        deps = ["some dependency"],
    )
    
    go_binary(
        name = "my_tool",
        embed = [":my_tool_lib"],
        visibility = ["//visibility:public"],
    )

So the idea is when I hit bazel run, it will build the my_tool go binary, which the go test my_test can use (see the deps field of the go test).

While in the CI I hit this error:


    ERROR: /home/agent/work/.go/src/some/of/my/path/BUILD.bazel:20:8: in go_test rule //some/of/my/path:my_test:
    Traceback (most recent call last):
      File "/home/agent/.cache/bazel/_bazel_agent/40f5e2a2e18a7cdb4cd075f919d8072b/external/io_bazel_rules_go/go/private/rules/test.bzl", line 66, column 43, in _go_test_impl
        internal_source = go.library_to_source(go, ctx.attr, internal_library, ctx.coverage_instrumented())
      File "/home/agent/.cache/bazel/_bazel_agent/40f5e2a2e18a7cdb4cd075f919d8072b/external/io_bazel_rules_go/go/private/context.bzl", line 247, column 26, in _library_to_source
        _check_binary_dep(go, dep, "deps")
      File "/home/agent/.cache/bazel/_bazel_agent/40f5e2a2e18a7cdb4cd075f919d8072b/external/io_bazel_rules_go/go/private/context.bzl", line 295, column 13, in _check_binary_dep
        fail("rule {rule} depends on executable {dep} via {edge}. This is not safe for cross-compilation. Depend on go_library instead.".format(
    Error in fail: rule //some/of/my/path:my_test depends on executable //some/of/my/path/my_tool:my_tool via deps. This is not safe for cross-compilation. Depend on go_library instead.
    ERROR: Analysis of target '//some/of/my/path:my_test' failed; build aborted: Analysis of target '//some/of/my/path:my_test' failed
    INFO: Elapsed time: 79.552s
    INFO: 0 processes.
    FAILED: Build did NOT complete successfully (595 packages loaded, 12182 targets configured)
    ERROR: Build failed. Not running target
    FAILED: Build did NOT complete successfully (595 packages loaded, 12182 targets configured)
    Process exited with code 1

But my goal is to use the binary. How should I change the configs to achieve that?

ANSWER

Answered 2022-Jan-24 at 20:06

You want data, not deps. deps is for things linked into a binary, data is for things the binary uses at runtime.

Once your binary is in data, use runfiles.go to run it. Add @io_bazel_rules_go//go/tools/bazel:go_default_library to deps (it's a library you want linked in), and then use FindBinary to find the path.

Source https://stackoverflow.com/questions/70818261

QUESTION

Bazel build docker container with local golang module

Asked 2021-Nov-17 at 08:43

Let me start by saying I'm new to Bazel. I am trying to build a Docker container from a golang project that contains local module references.

First I'm creating a local golang module:

go mod init go-example

Here is the general project structure:

.
├── BUILD.bazel
├── WORKSPACE
├── cmd
│   └── hello
│       ├── BUILD.bazel
│       └── main.go
├── go.mod
├── go.sum
└── pkg
    └── echo
        ├── BUILD.bazel
        └── echo.go

In main.go I am importing pkg/echo from the local module.

import (
    "go-example/pkg/echo"
)

(top level BUILD.bazel)

...

# gazelle:prefix go-example

✅ Default bazel build works

$ bazel run //:gazelle
$ bazel build //cmd/hello

❌ Docker build fails. I get the following error:

(cmd/hello/BUILD.bazel)

...

go_image(
    name = "docker",
    srcs = ["main.go"],
    importpath = "go-example/cmd/hello",
)

$ bazel build //cmd/hello:docker
...
compilepkg: missing strict dependencies:
    /private/var/tmp/_bazel[...]/__main__/cmd/hello/main.go: import of "go-example/pkg/echo"
No dependencies were provided.

ANSWER

Answered 2021-Nov-17 at 08:43

Figured it out, posting here if anyone else stumbles on this.

The answer is simple - you need to embed the go_library rule within the go_image rule. Here is my cmd/hello/BUILD.bazel where I also embed the go image in a docker container

load("@io_bazel_rules_go//go:def.bzl", "go_binary", "go_library")
load("@io_bazel_rules_docker//go:image.bzl", "go_image")
load("@io_bazel_rules_docker//container:container.bzl", "container_image")

go_library(
    name = "hello_lib",
    srcs = ["main.go"],
    importpath = "go-example/cmd/hello",
    visibility = ["//visibility:private"],
    deps = ["//pkg/echo"],
)

go_binary(
    name = "hello",
    embed = [":hello_lib"],
    visibility = ["//visibility:public"],
)

go_image(
    name = "hello_go_image",
    embed = [":hello_lib"],
    goarch = "amd64",
    goos = "linux",
    pure = "on",
)

container_image(
    name = "docker",
    base = ":hello_go_image",
)

Now it works to run bazel build //cmd/hello:docker

Source https://stackoverflow.com/questions/69982637

QUESTION

Golang: fatal error: unexpected signal during runtime execution

Asked 2021-Oct-29 at 20:27

I am randomly getting the following error when I am executing the binary (sometime it works):

fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x47 pc=0x7f07a019b448]

Here is the entire stacktrace.

The OS version where I am running the binary:

NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Go version:

go version
go version go1.16.9 linux/amd64

Bazel options:

go_binary(
    name = "app-operator",
    embed = [":app-operator_lib"],
    gc_linkopts = [
        "-linkmode",
        "external",
        "-extldflags",
        "-static",
    ],
    static = "on",
    visibility = ["//visibility:public"],
)

I think it's happening in this goroutine:

goroutine 408 [select]:
net/http.(*Transport).getConn(0x22f49e0, 0xc00080b440, {{}, 0x0, {0x16482cc, 0x4}, {0xc0006d9590, 0x30}, 0x0})
    GOROOT/src/net/http/transport.go:1372 +0x5d2
net/http.(*Transport).roundTrip(0x22f49e0, 0xc0005b0400)
    GOROOT/src/net/http/transport.go:581 +0x774
net/http.(*Transport).RoundTrip(0x30, 0x1817c80)
    GOROOT/src/net/http/roundtrip.go:18 +0x19
net/http.send(0xc0005b0400, {0x1817c80, 0x22f49e0}, {0x15f8740, 0x201, 0x0})
    GOROOT/src/net/http/client.go:252 +0x5d8
net/http.(*Client).send(0x2382ea0, 0xc0005b0400, {0x380, 0x0, 0x0})
    GOROOT/src/net/http/client.go:176 +0x9b
net/http.(*Client).do(0x2382ea0, 0xc0005b0400)
    GOROOT/src/net/http/client.go:725 +0x908
net/http.(*Client).Do(...)
    GOROOT/src/net/http/client.go:593
somecompany.com/operators/app-operator/http/client.(*APIClient).callAPI(0xc00078e030, 0xc0005b0400)
    operators/app-operator/http/client/client.go:151 +0x12e
somecompany.com/operators/app-operator/http/client.(*BackuprestoreApiService).Poll(0xc0004de148, 0xc00016b8a8)
    operators/app-operator/http/client/api_backuprestore.go:216 +0x5bd
somecompany.com/operators/app-operator/controllers.(*BackupReconciler).Poll(0xc0004de120, {0xc00076a4b0, {0xc00021c268, 0xc00016ba38}, 0xc00076a4c0})
    operators/app-operator/controllers/backup_controller.go:165 +0x16d
somecompany.com/operators/app-operator/controllers.(*BackupReconciler).Poll(0xc0004de120, {0xc00076a4b0, {0xc00021c268, 0x4f416a}, 0xc00076a4c0})
    operators/app-operator/controllers/backup_controller.go:186 +0x396
somecompany.com/operators/app-operator/controllers.(*BackupReconciler).Poll(0xc0004de120, {0xc00076a4b0, {0xc00021c268, 0x4f4226}, 0xc00076a4c0})
    operators/app-operator/controllers/backup_controller.go:186 +0x396
somecompany.com/operators/app-operator/controllers.(*BackupReconciler).Backup(0xc0004de120, 0xc0006ab4a0)
    operators/app-operator/controllers/backup_controller.go:147 +0x396
somecompany.com/operators/app-operator/controllers.(*BackupReconciler).createBackupHandler(0xc00016bd78, 0x183e758)
    operators/app-operator/controllers/backup_controller.go:93 +0x1d
somecompany.com/operators/app-operator/controllers.(*BackupReconciler).Reconcile(0xc0004de120, {0x183e758, 0xc000772d50}, {{{0xc0000596b8, 0x155d9a0}, {0xc0000596b0, 0xc000338100}}})
    operators/app-operator/controllers/backup_controller.go:87 +0x1c5
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler(0xc0000da320, {0x183e6b0, 0xc0000b4000}, {0x14fda20, 0xc0009a4000})
    external/io_k8s_sigs_controller_runtime/pkg/internal/controller/controller.go:298 +0x303
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem(0xc0000da320, {0x183e6b0, 0xc0000b4000})
    external/io_k8s_sigs_controller_runtime/pkg/internal/controller/controller.go:253 +0x205
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2()
    external/io_k8s_sigs_controller_runtime/pkg/internal/controller/controller.go:214 +0x85
created by sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2
    external/io_k8s_sigs_controller_runtime/pkg/internal/controller/controller.go:210 +0x354

ANSWER

Answered 2021-Oct-29 at 20:27

You should be able to remove the gc_linkopts options from the build. Statically linking glibc is not really supported, and may be causing problems.

If you have other cgo libraries you need to link statically, you will need to provide the linker flags for those libraries specifically.

If the only use of cgo is for name resolution on linux, you can almost always build without cgo and rely on the native Go implementations when a static binary is desired without a portable C implementation.

Source https://stackoverflow.com/questions/69773478

QUESTION

How to do configuration and variant handling in Bazel?

Asked 2021-Oct-15 at 23:59

Been reading the Bazel docs over and over to the point where nothing feels new, but I cannot seem to grasp how to setup configurations and variants for variants other than the native ones, e.g. --cpu and --compilation_mode.

To explain what I mean with configuration and variants, consider this table of Configuration rows, and Variant Points columns, and Variant cells (making this table up, hope it at least makes abstract sense):

	Has hardware module X	Connected on interface	Fail fast
Customer configuration 1	Yes	Ethernet	Yes
Customer configuration 2	Yes	USB	Yes
Customer configuration 3	No	USB	No
Debug hw configuration	No	UART	Yes

From a Bazel user perspective:

All targets should be buildable for all configurations by default
- Not ok adding "Customer configuration X" everywhere on adding a configuration
- Configuration specific components should be possible to explicitly state which configuration it is specific to
  - I think this is what constraint_value is for
Rules should add flags based on configuration
- For example -DVARIANT_POINT_CONNECTED_ETH for Ethernet connection and -DVARIANT_POINT_CONNECTED_USB for USB connection
I want a simple build command for building/testing/running a single configuration
- Something like bazel build //my/target --//:configuration=debughw
- Think there is something about it in the skylark config docs, but not seeing how to go from the example to using constraint_values and select() in rules

ANSWER

Answered 2021-Oct-15 at 23:59

You're looking for platforms. Build settings (that you found first) are better for independent pieces of configuration where setting them in any permutation is useful, vs platforms tie all the pieces together. The resulting settings and constraints can then be used to drive compiler flags and limit targets to certain configurations.

For your example, I think something like this makes sense:

constraint_setting(name = "has_x")

constraint_value(
    name = "x_v1",
    constraint_setting = ":has_x",
)

constraint_value(
    name = "x_v2",
    constraint_setting = ":has_x",
)

constraint_value(
    name = "x_none",
    constraint_setting = ":has_x",
)

constraint_setting(name = "interface")

constraint_value(
    name = "interface_usb",
    constraint_setting = ":interface",
)

constraint_value(
    name = "interface_ethernet",
    constraint_setting = ":interface",
)

constraint_value(
    name = "interface_uart",
    constraint_setting = ":interface",
)

constraint_setting(name = "failure_reporting")

constraint_value(
    name = "fail_fast",
    constraint_setting = ":failure_reporting",
)

constraint_value(
    name = "fail_bugreport",
    constraint_setting = ":failure_reporting",
)

platform(
    name = "customer_1",
    constraint_values = [
        "@platforms//os:linux",
        "@platforms//cpu:x86_64",
        ":x_v1",
        ":interface_ethernet",
        ":fail_fast",
    ],
)

platform(
    name = "customer_2",
    constraint_values = [
        "@platforms//os:linux",
        "@platforms//cpu:x86_64",
        ":x_v1",
        ":interface_usb",
        ":fail_fast",
    ],
)

platform(
    name = "customer_3",
    constraint_values = [
        "@platforms//os:linux",
        "@platforms//cpu:x86_64",
        ":x_none",
        ":interface_usb",
        ":fail_bugreport",
    ],
)

platform(
    name = "debug_hw",
    constraint_values = [
        "@platforms//os:linux",
        "@platforms//cpu:x86_64",
        ":x_none",
        ":interface_uart",
        ":fail_fast",
    ],
)

Notice how each platform specifies a setting for each of the constraints. A given compiler command (created by the configured target) will use exactly one platform. Also, each file will be compiled separately for every platform even if the outputs are identical. Platforms are intended to limit which permutations of the constraints are actually built. If you want to deduplicate the constraints, platform.parents lets you build an inheritance tree of platforms, you can't use two platforms at the same time.

The target_compatible_with attribute limits targets to specific constraint values. By default, every target is considered compatible with all platforms. If you use target_compatible_with to limit this, then incompatible targets will produce errors if you try to build them explicitly or just be skipped if included as part of a wildcard. For your use case, this target would build for any of the platforms:

cc_library(
    name = "generic_linked_list",
    <etc>
)

but this one would only build for customer_1 and customer_2:

cc_library(
    name = "hardware_x_driver",
    target_compatible_with = [":x_v1", ":x_v2"],
    <etc>
)

cc_library(
    name = "ethernet_driver",
    # Or you could have a separate constraint for "has ethernet hardware",
    # to use for some platforms which have the hardware but don't use it
    # as the primary interface.
    target_compatible_with = [":interface_ethernet"],
    <etc>
)

Using different compiler flags, dependencies, or most other rule attributes for different platforms is done with select. Select can read the constraint_values directly. So you could write this:

cc_library(
    name = "selected_connection",
    copts = select({
        ":interface_usb": [ "-DVARIANT_POINT_CONNECTED_USB" ],
        ":interface_ethernet": ["-DVARIANT_POINT_CONNECTED_ETH" ],
        ":interface_uart": ["-DVARIANT_POINT_CONNECTED_UART" ],
    }),
    deps = select({
        ":interface_ethernet": [ ":ethernet_driver" ],
        "//conditions:default": [],
    }),
    <etc>
)

Note that if you want the defines to propagate to dependent targets, use cc_library.defines instead of copts. Also, using cc_library.local_defines would give the same non-inheriting semantics and also be compatible with compilers that use a different command-line flag for that.

The easiest way to specify a platform is with --platforms. In this case, build with something like --platforms=//:customer_1. You can specify that directly on the command line or put it a .bazelrc config section like this:

build:customer_1 --platforms=//some/long/and/annoying/package:customer_1

which you would use with --config=customer_1.

Source https://stackoverflow.com/questions/69580604

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install bazel

Install Bazel
Get started with Bazel
Follow our tutorials: Build C++ Build Java Android iOS

Support

Bazel command lineRule referenceUse the query commandExtend BazelWrite testsRoadmapWho is using Bazel?

Find more information at:

Reuse Trending Solutions

14 best Python Telegram Bot

21 best C# Game Development in 2023

Image Resizing using OpenCV in Python

How to Validate an Email Address in JavaScript

Age Calculator using JavaScript

28 best Python Face Recognition in 2023

Display Stopwatch in ReactJs

Google Maps Integration with Location

Disease Predictor

Resolving Gender Bias in AI

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 650 million Knowledge Items

Find more libraries

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Explore Kits

Save this library and start creating your kit

Clone

HTTPS

https://github.com/bazelbuild/bazel.git

CLI

gh repo clone bazelbuild/bazel

SSH

git@github.com:bazelbuild/bazel.git

Download

Rel.7.0.0-pre.20230118.2.zip

Rel.7.0.0-pre.20230118.2.tar

Rel.7.0.0-pre.20221212.2.zip

Rel.7.0.0-pre.20221212.2.tar

Rel.7.0.0-pre.20221207.2.zip

Rel.7.0.0-pre.20221207.2.tar

Share this Page

See Similar Libraries in

Utilities

Build Tool

Reuse Utilities Kits

Tetris Game

Open Source Intelligence

Ai Hulks App Kit

16 best Python Animation Libraries in 2023

11 best Python Regex libraries in 2023

See all related Kits

Consider Popular Build Tool Libraries

by jackfrued

by webpack

by parcel-bundler

by evanw

by composer

See all Build Tool Libraries

Try Top Libraries by bazelbuild

by bazelbuild Go

by bazelbuild Go

by bazelbuild Go

by bazelbuild Go

by bazelbuild Java

See all Libraries by this author

Compare Build Tool Libraries with Highest Support

by bazelbuild

by webpack

by spack

by pypa

by gradle

See all Build Tool Libraries

Compare Build Tool Libraries with Highest Quality

by fabiofalci

by nuecho

by forge

by mrice

servlet3-maven-archetype

by maciejwalkowiak

See all Build Tool Libraries

Compare Build Tool Libraries with Highest Security

by ashri

by yueyueniao2012

by fabiofalci

by Docracy

example-ratpack-gradle-java-app

by ratpack

See all Build Tool Libraries

Compare Build Tool Libraries with Permissive License

java-wordpress-api

by ashri

moco-maven-plugin

by garrettheel

gradle-in-action-source

by bmuschko

license-check

by mrice

coveralls-maven-plugin

by trautonen

See all Build Tool Libraries

Compare Build Tool Libraries with Highest Reuse

by atteo

by Netflix

by alx3apps

by xcesco

by googleapis

See all Build Tool Libraries

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 650 million Knowledge Items

Find more libraries

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Explore Kits

Save this library and start creating your kit

Open Weaver – Develop Applications Faster with Open Source

kandi

Develop Custom Functions

Develop Projects with Kits

Explore Popular Libraries

Product Tour

FAQ

Community and Support

Live Bootcamps

Self Paced Certifications

Hackathons and Events

Company

Terms
Privacy policy

bazel | a fast , scalable , multi-language and extensible build system | Build Tool library

kandi X-RAY | bazel Summary

bazel Key Features

bazel Examples and Code Snippets

Community Discussions

Trending Discussions on bazel

Vulnerabilities

Install bazel

Support

Reuse Trending Solutions

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Clone

Download

Reuse Utilities Kits

Consider Popular Build Tool Libraries

Try Top Libraries by bazelbuild

Compare Build Tool Libraries with Highest Support

Compare Build Tool Libraries with Highest Quality

Compare Build Tool Libraries with Highest Security

Compare Build Tool Libraries with Permissive License

Compare Build Tool Libraries with Highest Reuse

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

Reuse Solution Kits and Libraries Curated by Popular Use Cases

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 650 million Knowledge Items

Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from
over 650 million Knowledge Items