How to add a framework target as a target dependency of the main app, but exclude it from "link binary with libraries"

[longvudai]

Hi,

I define a macOSBridging framework target in project. I want to add macOSBridging to catalyst-searchbar as target dependency, but tuist also include macOSBridging in "link binary with libraries" section.

Can I exclude macOSBridging from this section with tuist config?

[pepicrft]

What's the use case for adding it as a target dependency but not linking it?

[longvudai]

I want to use some AppKit API in my catalyst app with the instructions below.
how-to-add-a-search-bar-to-a-maccatalyst-application

If I link the macOSBridging framework, I get the message: framework 'macOSBridging' not found

[pepicrft]

Gotcha! What I'd do in that case is to disable the linking if it's a Catalyst app target, depending on a MacOS library. What do you think?

[longvudai]

Yes. I think it should work in this case. But it would be great if we could control linking manually by parameter for example

[pepicrft]

But it would be great if we could control linking manually by parameter for example

This is the complexity that motivated the creation in the first place. Therefore, I do not favor bringing it back as an escape hatch. If there are new dependency scenarios that we need to handle, let's understand them and incorporate them into our abstractions.

I'll convert this to an issue.