When maintaining two build systems (Xcode and Bazel) it's useful to be able to configure what is and isn't generated. In our case, we only generate modulemaps for frameworks which enable this feature in our Xcode setup. In bazel however, this file is generated regardless.
This leads to build inconsistency where Xcode fails to build because a missing modulemap is not found while Bazel continues to pass since these are always generated.
Instead, we should allow users to enable/disable this behavior. With this change generate_default_modulemap will be defaulted to True (so no changes here) unless you set to False in which case no modulemap is generated.
When maintaining two build systems (Xcode and Bazel) it's useful to be able to configure what is and isn't generated. In our case, we only generate modulemaps for frameworks which enable this feature in our Xcode setup. In bazel however, this file is generated regardless.
This leads to build inconsistency where Xcode fails to build because a missing modulemap is not found while Bazel continues to pass since these are always generated.
Instead, we should allow users to enable/disable this behavior. With this change
generate_default_modulemap
will be defaulted toTrue
(so no changes here) unless you set toFalse
in which case no modulemap is generated.