tree 7bc45c40f49541e0986ee611bb90f29f6d546dba
parent 9a0e53e6d1542cf11e6213e7121cfc19a363ec34
author Mark Elliot <123787712+mark-thm@users.noreply.github.com> 1713229675 -0400
committer GitHub <noreply@github.com> 1713229675 -0400
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsFcBAABCAAQBQJmHc9rCRC1aQ7uu5UhlAAAJr4QADbWg5Hp+v/NTZTjGgsV032G
 HcqMLurbgDAayp7FUgPDmWHvZ/c8sEkpCniWRLtssHYIp9s6jIUR5EtX30d1dhTe
 M18gExhqCDW7iRiLc/CHPrggHnxT+lynLMEqyFC7K7kYsKQ/58OFYybVWGF3rPMi
 3JgQB/gysjYwXWG0J3QQX8lqr+e7EVGpgOe7pQ+UXeXuwVue6p6dZCJMqC14L1WB
 3SPSYswZq1TFZjl87aIrpcjqH4jdPYD2YXE8Umt5kwgbS26C2VpUZlFZFzMjn4OM
 K5IcP5dMRLF+iWEi9m6e1AnJlvrGO2Fffi5XT5DfFsLS+rbjfYNfyUbWbMU+QVc4
 SnOw4HIL/jpHxWHkaViPsVadKucuh834VAujcjfnvvQb9XIbuWvWxcC3tuMBUUbU
 buIuXS+0FGedXkiEuaNtgDqn491e2/onzwyGQ1jclRXLjZ4+FtgADKAd1QVtY16b
 Mhtalhq0PYJxfMZJfHJBak9zL+KY5qWNt2eTA2BfQN2AV50Mu/hEqm4W8IcgdRLP
 ntOr9Uik3F5ciZ+P+kquSwxcQfpFoStZ5ieSg1wIk+e1PoNNO14jqTSAgYM7VY9S
 4PEU8ZO25O9SHH44P3D233QghBxEPTucd+nQTy0pO63hgv+bZ2+yBfBizT0emqvO
 SLz8Hu2o8xjWFrBvREP6
 =Wl5v
 -----END PGP SIGNATURE-----
 

Add convenience target for running in the current working directory (#29)

It's common for users of multitool to want to run tools in the current working directory. In #26, @alexeagle documented a technique we've used for a while with creating a script and symlinking to it. Our internal copy of this script is a bit more complicated to help avoid expensive calls to Bazel that simple `bazel run` calls don't really need. More refinements have been proposed in #27. All of these things are fundamentally workarounds for https://github.com/bazelbuild/bazel/issues/3325.

To help simplify things, this PR adds a convenience wrapper that captures the execpath, switches to $BUILD_WORKING_DIRECTORY, and then runs the desired tool. The resulting shell script gets to use a very simple `bazel run`, should be compatible across any slew of Bazel options, and cache as well as any typical run target.