Quantcast
Channel: Package Manager - Swift Forums
Viewing all articles
Browse latest Browse all 166

Versioning for packages that depend on packages that require -ObjC

$
0
0

Hi all,

I'm currently developing a Swift package that depends on a number of 3rd party frameworks (one example is Firebase) that require the -ObjC linker flag added to be linked correctly.

The problem is, when listing it as a dependency in the Package definition, when I add the -ObjC flag like this, I can no longer use resolution with actual version numbers and resort to branch based resolution.

.target(
    name: "FrameworkName",
    dependencies: [
        .product(name: "FirebaseAnalytics", package: "firebase-ios-sdk"),
        .......
        .......
    ],
    linkerSettings: [
        .unsafeFlags(["-ObjC"])
    ]
),

Is there a way to do this without using unsafeFlags? SPM is really problematic when it comes to updating private packages from our bitbucket account (it frequently fails to update these packages unless we reset the package caches), and not being able to use the version number makes it very difficult to determine whether it actually updated the package or not.

4 posts - 3 participants

Read full topic


Viewing all articles
Browse latest Browse all 166

Trending Articles