Multiple commands produce 'xxx/RswiftGeneratePublicResources/xxx/R.generated.swift'

[RobertDresler]

Hello,

I have iOS app which has embedded watchOS app. I also have SPM package which runs R.swift plugin:

.target(
    name: "VOSStrings",
    dependencies: [.product(name: "RswiftLibrary", package: "R.swift")],
    resources: [.process("Resources")],
    plugins: [.plugin(name: "RswiftGeneratePublicResources", package: "R.swift")]
)

This package is added to both targets: the main iOS app and its embedded watchOS app. Unfortunately, I am unable to build the app since I receive the error Multiple commands produce 'xxx/RswiftGeneratePublicResources/xxx/R.generated.swift'

When I remove watchOS app from target dependencies of iOS app, it works, but then iOS app can't be built. Don't you know what could be wrong?

Thank you!

[SpectatorNan]

i have the same error, but i delete old R.generated.swift file and then rebuild project success

[LP-sleep]

I use 7.3.0, which does not need to add R.geratated.swift to your target, only need to add script in accordance with SPM access steps to build and then R.xxx can used. It is worth noting that the name of the struct is changed to _R, and the Struct can extension with _R struct.

[RobertDresler]

@SpectatorNan unfortunetely, this doesn't solve the problem for me since I use SPM where storing this file is out of my control.

[RobertDresler]

@tomlokhorst here is minimal reproducible example. Don't you know, what could be wrong?
https://github.com/RobertDresler/RSwift-in-shared-package

[tomlokhorst]

Thanks for the minimal reproducible example, that is very useful!

I'm no expert on the Xcode build system, so I'm not exactly sure what's going on.

But I did manage to the the example building, with some changes:

• I removed the reference to Strings from both targets
• I added a new Framework target, that does use Strings
• I included that new framework in both original targets

Again, I'm not exactly sure, but I think the difference with this indirection is that the new framework is dynamically linked, and the original Strings library was statically linked (twice).

[saltyskip]

Anyone able to find the root cause of this issue?

[RobertDresler]

@saltyskip Creating two different targets overcomes the problem (see my question on SO). Eventough it doesnt solve it as I would like to, I don't know any better solution so far.

If you need to have targets A and A_watchOS, and you have target B which is imported by both iOS and watchOS app targets, you can create B which imports A and A_watchOS based on platform condition in SPM.

[realityworks]

This is a blocker for us. We have two schemes and one target. Fails because it thinks it needs to build for both schemes...

Reverting to R.swift 6.