Skip to content

feat: iOS static linking improvement #379

@sydneyagcaoili

Description

@sydneyagcaoili

Description

Users who employ static linking in their applications are currently unable to successfully build their projects if they also include other statically linked libraries (e.g., Rive). The build process terminates with errors like "symbols not found" or "duplicate symbols," indicating a deep conflict in the linked binaries. This effectively prevents the use of your library in certain common application architectures.

Requirements

[ ] Ensure compatibility with static linking environments to avoid conflicts with other libraries.

Update(Dec 2, 2025):

Replication steps

  • Podfile's use_frameworks:
    use_frameworks! :linkage => :static
  • Dependencies (Example from @alnitak)
  rive: ^0.14.0-dev.14
  flutter_soloud: ^3.4.5

Result

Failed to build iOS app
Error (Xcode): Building for 'iOS-simulator', but linking in object file (/Users/........../.pub-cache/hosted/pub.dev/flutter_soloud-3.4.5/ios/libs/libflac_iOS-device.a[2](bitmath.o)) built for 'iOS'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions