root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 3 Packages Projects Releases Wiki Activity
rabbitmq-server/bazel/BUILD.emqtt

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

141 lines
2.9 KiB
Plaintext
Raw Normal View History

Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
load("@rules_erlang//:erlang_bytecode2.bzl", "erlang_bytecode", "erlc_opts")
load("@rules_erlang//:erlang_app.bzl", "erlang_app")
erlc_opts(
name = "erlc_opts",
values = select({
"@rules_erlang//:debug_build": [
"+debug_info",
"+warn_export_all",
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
"+warn_obsolete_guard",
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
"+warn_shadow_vars",
"+warn_unused_import",
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
"+warn_unused_vars",
Adjust bazel/BUILD.emqtt until https://github.com/rabbitmq/rules_erlang/pull/147 is released
2023-02-17 02:15:03 +08:00
"-DBUILD_WITHOUT_QUIC", # keep
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
],
"//conditions:default": [
"+debug_info",
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
"+deterministic",
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
"+warn_export_all",
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
"+warn_obsolete_guard",
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
"+warn_shadow_vars",
"+warn_unused_import",
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
"+warn_unused_vars",
Adjust bazel/BUILD.emqtt until https://github.com/rabbitmq/rules_erlang/pull/147 is released
2023-02-17 02:15:03 +08:00
"-DBUILD_WITHOUT_QUIC", # keep
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
],
}),
visibility = [":__subpackages__"],
)
erlang_bytecode(
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
name = "other_beam",
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
srcs = [
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
"src/emqtt.erl",
"src/emqtt_cli.erl",
"src/emqtt_frame.erl",
"src/emqtt_inflight.erl",
"src/emqtt_props.erl",
"src/emqtt_quic.erl",
"src/emqtt_secret.erl",
"src/emqtt_sock.erl",
"src/emqtt_ws.erl",
],
outs = [
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
"ebin/emqtt.beam",
"ebin/emqtt_cli.beam",
"ebin/emqtt_frame.beam",
"ebin/emqtt_inflight.beam",
"ebin/emqtt_props.beam",
"ebin/emqtt_quic.beam",
"ebin/emqtt_secret.beam",
"ebin/emqtt_sock.beam",
"ebin/emqtt_ws.beam",
],
Rebuild bazel/BUILD.* files with recent rules_erlang rules_erlang 3.9.5+ generates "compact" rules when running update-repos this speeds up the cold build, since fewer erlc actions are run, and since external deps typically don't change incrementally, the value of having a bazel rule per file is miminal
2023-02-17 00:43:49 +08:00
hdrs = [
"include/emqtt.hrl",
"include/logger.hrl",
],
app_name = "emqtt",
beam = [],
erlc_opts = "//:erlc_opts",
)
filegroup(
name = "beam_files",
srcs = [":other_beam"],
Use gazelle for external erlang deps (#6935) * Add gazelle for use with update-repos command * Use explicit BUILD.app_name files for erlang app deps This allows us to remove the duplicate definitions in workspace_helpers.bzl These files are generated with gazelle. For instance: BUILD.ra is generated with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel hex.pm/ra@2.4.6` Running gazelle this way will modify the WORKSPACE file, as gazelle does not yet support MODULE.bazel files. Such changes to the WORKSPACE can be dropped, and should not be committed. It may also update the `moduleindex.yaml` file. Changes to `moduleindex.yaml` should be committed. However * skip the explicit bazel/BUILD.osiris file, as osiris already contains the file in its repo * skip the explict BUILD.inet_tcp_proxy_dist file, since the repo already contains a bazel BUILD.bazel file gazelle command: `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel inet_tcp_proxy_dist=github.com/rabbitmq/inet_tcp_proxy@master` * jose is imported with `bazel run gazelle -- update-repos --verbose --build_files_dir=bazel jose=github.com/michaelklishin/erlang-jose@d63c1c5c8f9c1a4f1438e234b886de8607a0034e` * Move the bats dep directly to WORKSPACE, drop workspace_helpers.bzl * Use bzlmod in windows tests
2023-01-25 16:41:56 +08:00
)
filegroup(
name = "srcs",
srcs = [
"src/emqtt.app.src",
"src/emqtt.erl",
"src/emqtt_cli.erl",
"src/emqtt_frame.erl",
"src/emqtt_inflight.erl",
"src/emqtt_props.erl",
"src/emqtt_quic.erl",
"src/emqtt_secret.erl",
"src/emqtt_sock.erl",
"src/emqtt_ws.erl",
],
)
filegroup(
name = "private_hdrs",
srcs = [],
)
filegroup(
name = "public_hdrs",
srcs = [
"include/emqtt.hrl",
"include/logger.hrl",
],
)
filegroup(
name = "priv",
srcs = [],
)
filegroup(
name = "licenses",
srcs = ["LICENSE"],
)
filegroup(
name = "public_and_private_hdrs",
srcs = [
":private_hdrs",
":public_hdrs",
],
)
filegroup(
name = "all_srcs",
srcs = [
":public_and_private_hdrs",
":srcs",
],
)
erlang_app(
name = "erlang_app",
srcs = [":all_srcs"],
hdrs = [":public_hdrs"],
app_name = "emqtt",
beam_files = [":beam_files"],
deps = [
"@cowlib//:erlang_app",
"@getopt//:erlang_app",
"@gun//:erlang_app",
],
)
alias(
name = "emqtt",
actual = ":erlang_app",
visibility = ["//visibility:public"],
)