jheaff1

Could you instead use https://bazel.build/docs/user-manual#per-file-copt I don’t believe these are propagated by rules_foreign_cc

The libffi issue is that the build target defined in the rules_foreign_cc examples expects the .so file to have the path lib/x86_64-linux-gnu/libffi.so.7.1.0. Yet in your build, the generated so file...

The gettext issue is because for Linux, there are no output shared libs specified in the BUILD file. Rules_foreign_cc expects the build to generate lib.a on Linux if the Bazel...

Also, it shouldn’t be necessary to build gettext for Linux as it is built into gcc. This is why the BUILD file for gettext is not complete for all platforms,...

Hi @pcj. Apologies for being unclear. Like the [cpptools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) extension, the bazel-stack-vscode extension downloads a number of artefacts from the internet during installation. If the bazel-stack-vscode extension .vsix file were...