It also works on my Mac Mini M1 and gives a nice ~2x speed increase! 🚀

$ cd ~/bin
$ curl -LO https://github.com/bazelbuild/bazel/releases/download/4.0.0/bazel-4.0.0-darwin-x86_64
$ chmod +x ~/bin/bazel-4.0.0-darwin-x86_64

$ cd ~/src && git clone https://github.com/bazelbuild/bazel.git && cd bazel
$ bazel-4.0.0-darwin-x86_64 build --cpu=darwin_arm64 -c opt //src:bazel
INFO: Elapsed time: 495.900s, Critical Path: 148.84s
INFO: Build completed successfully, 2884 total actions

$ mv bazel-bin/src/bazel ~/bin/bazel
$ bazel clean --expunge
$ bazel build --cpu=darwin_arm64 -c opt //src:bazel
INFO: Elapsed time: 255.364s, Critical Path: 68.15s
INFO: Build completed successfully, 2884 total actions

Pretty odd. Also running into this issue. For some weird reason, I can get it to work if I first place the data dependency in a sh_library() and then drag that sh_library() in as data of the sh_binary().

Thanks! Ran into this issue today in version 3.3.0, was able to work around it with this method.

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

<!-- need_author_cla -->

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

<!-- need_author_cla -->

Internal change.

Thanks, I'll start the import on this on Monday

Cleaned everything up, PTAL

done.

done.

Sorry had my IDE setting misconfigured

There remains a situation in which a workaround is not presently possible: if you want to declare a directory and some subset of files beneath it. Say you know the primary output but not some additional outputs which may also be generated and need to be kept. Currently:

def _impl(ctx):
    resources = ctx.actions.declare_directory("{name}.d".format(name = ctx.label.name))
    primary_output = ctx.actions.declare_file("{name}.d/{name}.html".format(name = ctx.label.name))
    ctx.actions.run_shell(
        command = "touch \"$@\"",
        outputs = [resources, primary_output],
        arguments = [primary_output.path],
    )
    return [DefaultInfo(files = depset([resources]))]

dir_and_file = rule(
    implementation = _impl,
)

Building that rule with RBE fails inside Bazel and no amount of mkdir in the script will fix that. While you can just declare the directory, it is useful for a variety of reasons to be able to have a File nominating both the primary output as well as the containing directory. With the current remote semantics, that's not possible.

kinda surprised -x wasn't here before

Resolves https://github.com/bazelbuild/bazel/issues/13122

Description of the problem / feature request:

Support stripping Swift symbols for binaries built for Apple platforms.

Feature requests: what underlying problem are you trying to solve with this feature?

There's currently no option to allow stripping Swift symbols for binaries built for Apple platforms. Since xcodebuild's ipa exporting supports that (and defaults to YES), I'd like to be able to do that here as well.

What operating system are you running Bazel on?

macOS

What's the output of bazel info release?

release 4.0.0

Have you found anything relevant by searching the web?

From the strip man page:

-T
The intent of this flag is to remove Swift symbols. It removes the symbols whose names
begin with `_$S' or `_$s' only when it finds an __objc_imageinfo section with and it has
a non-zero swift version. The future the implementation of this flag may change to match the intent.

From the xcodebuild -h page:

Available keys for -exportOptionsPlist:
        ...
        stripSwiftSymbols : Bool

                Should symbols be stripped from Swift libraries in your IPA? Defaults to YES.

I found two code paths referencing to code stripping but -T is not passed, and passing it via --stripopt doesn't take effect.

https://github.com/bazelbuild/bazel/blob/25768512a6c30cdc6af3098078ef02375fd5c914/src/main/java/com/google/devtools/build/lib/rules/objc/CompilationSupport.java#L1561-L1574

https://github.com/bazelbuild/bazel/blob/ef903e08b270f3fa3c4d36f8122876a892b47087/tools/osx/crosstool/cc_toolchain_config.bzl#L296-L311

It doesn't look like there's a consistent mnemonic to look-up, however?

There isn't, each language will have its own primary output Mnemonic. tbh there are probably few enough that you could hard-code them: Javac, GoLink, etc.

You could potentially write an aspect to look up the DefaultInfo Provider of the target, and either use that as-is or merge it with the above...

I've also recently realised that the correct behaviour is probably to have a final step that "publishes" artefacts to where you want them to be, but haven't had time to get my head around any subtleties in making that work with Bazel's hermetic / side-effect-averse design.

Internal change.