Forward environment variables to SPM about tuist

[ffittschen]

Hi, I just created a reproducible sample project and it turned out that some other 3rd party dependency in my original project depend on swift-nio-ssl as well, so it probably got skipped when resolving grpc-swift, but it was resolved through the others and then the graph command picked it up from there.

To recap, GRPC_NO_NIO_SSL=1 tuist install does seem to work as expected and does forward the env variable. I can't find any mention of swift-nio-ssl in the Package.resolved file of the sample project. And it is important to pass the same environment variable when running the graph command. Otherwise it will fail with an error, as it expects NIOSSL to be present, but it wasn't resolved when running tuist install.

Sample project

tuist-install-with-env-variable.zip

Steps

1. GRPC_NO_NIO_SSL=1 tuist install
   2a) tuist graph AppKit
   2b) GRPC_NO_NIO_SSL=1 tuist graph AppKit

2a) will fail with the error

NIOSSL is not a valid configured external dependency

2b) will succeed

Closing this issues as tuist is working as expected.

[fortmarek]

Hey 👋

What happens if you run the same steps but instead of tuist install, you run GRPC_NO_NIO_SSL=1 swift package resolve in the Tuist directory? Does tuist graph include the dependency or not?

A reproducible sample would be appreciated if you want us to look into it. If you want to take a look, that'd be amazing – if the issue is that we're not passing the initial env variables, then I would probably take a look here