Pedro Piñera Buendía

Thanks a lot @hiltonc for making this one happen 🙏🏼

Hi @jesus-mg-ios Thos preprocessor macros are added automatically based on the flavor of the configuration (debug or release). To my knowledge, we haven't changed anything recently in that area. If...

@DevVenusK do you have the link to that piece on https://translate.tuist.dev? I might need to change the source markdown for the segmentation to be right.

Hey @pacosw1 We are not maintaining the library actively, but we accept contributions. Feel free to make a contribution, or fork it and maintain it independently.

Sorry @noamfreeman. Sometimes @dosubot gets very inaccurate, and I believe it's the case here. I'd recommend to use the links at the bottom of their comments to flag that. Would...

Could you update to the latest version of the CLI and let us know if it works? There was a new Swift package API that Tuist did not support,

@nmcc24 this package was not designed for running on non-macOS platforms, so even if you make it compile, some features might not work. I'd suggest to use conditional linking when...

@nmcc24 thanks a lot for the context, I appreciate it. Wouldn't [`TargetDependencyCondition`](https://docs.swift.org/swiftpm/documentation/packagedescription/targetdependencycondition) be useful in this case, where you can declare a dependency conditionally based on the platform: ```swift Target(name:...

> If this can't be fully solved by Tuist in a reasonable way, maybe it could at least emit warnings/errors at generation time? > > I'd consider this pretty important...

@iteracticman I tried the repo [linked above](https://github.com/iteracticman/tuist-double-linking) with tuist 4.107.2 and I don't get any issues neither at generation time nor at runtime. Could you try to reproduce it with...