Closed luispadron closed 10 months ago
Seems like macos_dynamic_framework
doesn't create the .framework
file as expected according to: https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.html
It's missing the Versions/A
directory:
Lib.framework
├── Headers
│ └── Lib.h
├── Info.plist
├── Lib
└── Modules
├── Lib.swiftmodule
└── module.modulemap
Seems like
macos_dynamic_framework
doesn't create the.framework
file as expected according to: https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPFrameworks/Concepts/FrameworkAnatomy.html
So that's a rules_apple bug. We could fix it there.
I opened #2724 as a workaround for now. We want to disable that action anyway, since it's just extra overhead.
It's actually not super clear if that's the required format or if it's an option one can use for versioned frameworks.
It looks like rules_apple has examples of versioned frameworks but only via the import rules.
If you have a better idea of the bug this might be, mind reporting it @brentleyjones?
Description
When using a
macos_dynamic_framework
within amacos_application
target'sframework
attribute the generated Xcode project fails when building the app target with:This same build target works with a normal
bazel build
command.Reproduction steps
See the PR adding a
macos_dynamic_framework
target is failing when buildingmacOSApp
target: #2721Expected behavior
The
macos_dynamic_framework
target builds successfully.rules_xcodeproj version
main
Xcode version
15.0.0
Bazel version
main
rules_apple version
No response
rules_swift version
No response
Additional information
No response