Can you create a task for @jon to add cargo-lipo to the Nix environment?

I can package this for comm, but the project is currently considered deprecated. So I likely won't upstream it to nixpkgs. :/

In D4954#143549, @jon wrote:

I can package this for comm, but the project is currently considered deprecated. So I likely won't upstream it to nixpkgs. :/

Did we try the approach suggested by the author of the library in the section about "Maintenance Status"?

In D4954#143533, @ashoat wrote:

Can you create a task for @jon to add cargo-lipo to the Nix environment?

looks like Jon did this

In D4954#143552, @atul wrote:

In D4954#143549, @jon wrote:

I can package this for comm, but the project is currently considered deprecated. So I likely won't upstream it to nixpkgs. :/

Did we try the approach suggested by the author of the library in the section about "Maintenance Status"?

manually editing project.pbxproj seems pretty sketchy... it's a generated file, after all. but I'll make a linear task to look for a better approach. already talked to @tomek about investigating this

https://linear.app/comm/issue/ENG-1702/improve-grpc-client

pretty sure we can discard this now, actually. and cancel jon's linear task. depends on my updated Xcode diff being approved

Did we try the approach suggested by the author of the library in the section about "Maintenance Status"?

Yea, I would really prefer to not add yet-another-tool into the chain of assumptions. seems like specifying the platform triplet, and adding some run scripts should suffice to make those compilation targets available.