You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Generating an XCFramework with the project's build script leaves behind SwiftyBeaver's swiftinterface file necessitating SwiftyBeaver be included in the parent project. Simply changing BUILD_LIBRARY_FOR_DISTRIBUTION to true should fix this.
To Reproduce
Steps to reproduce the behavior:
Build (./build.sh xcframework 0.19.3 1)
Embed in another project
Build pukes on missing SwityBeaver fw (it is present on fs, missing its .swiftinterface file)
Expected behavior
Shouldn't have to include the dep in the parent project.
Additional context
Answer found in this SO post. Simply supplying the flag at the xcodebuild step doesn't work, it must be changed within the project file.
The text was updated successfully, but these errors were encountered:
e-001
changed the title
Building XCFramework doesn't include library deps (SwiftyBeaver)
Building XCFramework doesn't properly include framework deps (SwiftyBeaver)
Jul 8, 2021
Describe the bug
Generating an XCFramework with the project's build script leaves behind SwiftyBeaver's swiftinterface file necessitating SwiftyBeaver be included in the parent project. Simply changing
BUILD_LIBRARY_FOR_DISTRIBUTION
to true should fix this.To Reproduce
Steps to reproduce the behavior:
./build.sh xcframework 0.19.3 1
).swiftinterface
file)Expected behavior
Shouldn't have to include the dep in the parent project.
Additional context
Answer found in this SO post. Simply supplying the flag at the
xcodebuild
step doesn't work, it must be changed within the project file.The text was updated successfully, but these errors were encountered: