Tulsi generated project showing .pcm not found warnings as errors

[CognitiveDisson]

I still see this issue (#135) with Xcode 13 and Xcode 12.4. This behavior is observed only for the legacy build system.

I can reproduce this problem for my project using the master version of tulsi, Xcode 13 or Xcode 12. I have also checked that this behavior persists if I just echo this warning from the build phase script:

echo "warning: ./bazel-out/SomeTarget-AAAAAAAAAAAAA.pcm: No such file or directory"

This will be displayed as an error.

There was a fix for this problem, but it was reverted. Can we get this fix back?

fyi @thii

[thii]

Are you generating dSYMs for your debug builds?

[CognitiveDisson]

Are you generating dSYMs for your debug builds?

Yes

[thii]

Is there any reason for that? If you request dSYMs, the aspect build during the project generation would take almost as long as the normal build.

[CognitiveDisson]

Is there any reason for that? If you request dSYMs, the aspect build during the project generation would take almost as long as the normal build.

--apple_generate_dsym was needed for debugging, without it breakpoints don't work. I'm checking now if this problem is relevant. But in any case I expect that even when generating dSYMs this warning will not show up as an error.

[CognitiveDisson]

The breakpoint problem is no longer reproduced. Disabling dSYM generation ( SwiftForcesdSYMs = no ) removed this "pcm warning". Nevertheless, it would be nice to have this fix in case someone needs dSYM in a debug build.

[thii]

We can revert that if anyone has a use-case for it.

[keith]

Thanks for submitting this issue but this tool is being deprecated. Please checkout rules_xcodeproj for a more complete and maintained Xcode integration.