bazel
/
rules_foreign_cc
mirror of https://github.com/bazel-contrib/rules_foreign_cc
2
0
Fork 0
Code Issues Releases Activity
rules_foreign_cc/examples/toolchains_examples
History
James Sharpe 9a4435ecab
Attempt to catch shell script errors proactively with 'set -euo pipef… (#500) 
* Attempt to catch shell script errors proactively with 'set -euo pipefail'

* Fix up uninitialised variable use

* Fix osx shell function

* Fix to unbound variable in windows commands
 		2021-02-16 11:55:48 -08:00
..
.bazelrc Moved some additional examples into the examples directory (#509) 2021-02-16 08:13:25 -08:00
BUILD.bazel Moved some additional examples into the examples directory (#509) 2021-02-16 08:13:25 -08:00
README.md Moved some additional examples into the examples directory (#509) 2021-02-16 08:13:25 -08:00
WORKSPACE.bazel Moved some additional examples into the examples directory (#509) 2021-02-16 08:13:25 -08:00
additional_toolchains.bzl Moved some additional examples into the examples directory (#509) 2021-02-16 08:13:25 -08:00
fancy_platform_commands.bzl Attempt to catch shell script errors proactively with 'set -euo pipef… (#500) 2021-02-16 11:55:48 -08:00
test_platform_name_rule.bzl Moved some additional examples into the examples directory (#509) 2021-02-16 08:13:25 -08:00

README.md

How to add a shell toolchain implementation for a custom platform

(to modify the fragments of generated shell script)

  • define your own shell toolchain file(s) by copying @rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains/impl:linux_commands.bzl, and modifying the methods.
  • create a mapping: a list of ToolchainMapping with the mappings between created file(s) and execution or/and target platform constraints.
  • in the BUILD file of some package, call "registermappings" macro from "@rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains:defs.bzl", passing the mappings and toolchain_type = "@rules_foreign_cc//tools/build_defs/shell_toolchain/toolchains:shell_commands"
  • in the WORKSPACE file of your main repository, when you initialize rules_foreign_cc, pass the mappings and the package, in which BUILD file you called "register_mappings" macro

Please look how it is done in this example.