Skip to content

Assemble a versioned framework bundle for MacOS #353

Closed

Description

@kraenhansen

Trying to build a MacOS app using our Ferric example yields:

Framework /Users/kraenhansen/Library/Developer/Xcode/DerivedData/MacOSTestApp-eonuduoofvrnusfqfzhoueazhcsq/Build/Products/Debug/MacOSTestApp.app/Contents/Frameworks/ferric-example--ferric_example.framework contains Info.plist, expected Versions/Current/Resources/Info.plist since the platform does not use shallow bundles

From the "Validate MacOSTestApp.app" build phase.

We should make sure that Ferric assembles MacOS artefacts into a versioned framework:

if (versioned) {
// TODO: Add support for generating a Versions/Current/Resources/Info.plist convention framework
throw new Error("Creating versioned frameworks is not supported yet");
}

Activity

  1. shirakaba commented on Feb 10, 2026

    @shirakaba
    Collaborator

    Just linking previous conversations about versioned vs. unversioned frameworks: #261 #280

    I think I found that macOS apps need versioned frameworks. It might also have been that iOS doesn't support versioned frameworks, i.e. the two structures are mutually incompatible.

  2. self-assigned this
    on Feb 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions