> While Riff does its best to infer external dependencies from your project's crate dependencies
How does it do this? Just a list of known packages and their dependencies, or?
I'm using https://github.com/LaurentMazare/tch-rs/ (rust bindings for pytorch's c++ api). Depending on the hardware I'm building for I either need to download a cpu build of pytorch, or a cuda build of pytorch. How would this work with riff?
Is there any hope of a good cross compiling story? If so, that would be awesome (currently I just don't even try if there are significant C dependencies)!
How thoroughly are dependencies cached? Backed to the pytorch example it's a fairly big (and thus slow) download, I don't want that happening too frequently.
---
In general this looks like something that could be really useful. Using projects with significant C dependencies currently sort of sucks, and this looks like it might actually fix the problem :)
How does it do this? Just a list of known packages and their dependencies, or?
I'm using https://github.com/LaurentMazare/tch-rs/ (rust bindings for pytorch's c++ api). Depending on the hardware I'm building for I either need to download a cpu build of pytorch, or a cuda build of pytorch. How would this work with riff?
Is there any hope of a good cross compiling story? If so, that would be awesome (currently I just don't even try if there are significant C dependencies)!
How thoroughly are dependencies cached? Backed to the pytorch example it's a fairly big (and thus slow) download, I don't want that happening too frequently.
---
In general this looks like something that could be really useful. Using projects with significant C dependencies currently sort of sucks, and this looks like it might actually fix the problem :)