Open milyin opened 1 week ago
Actually in this case it does point to the error in build.rs - so it is sort of ok. The issue is if you have some syntax errors - given that cbingen is launched before actual build - you will get very difficult to read error information from cbindgen side instead of rustc - this can be achieved by first make a dry-run ignoring build.rs; the resulting binaries would still be cached by cargo of future reuse - so it should not affect the build time.
When subproject build-resources/opaque-types fails to build, it's not reported by build.rs To reproduce go to build-resources/opaque-types/src/lib.rs, add any syntax error, and run "cargo check" in the main project.
The output is:
This doesn't point to real cause of error. If error was introduced not directly into "build-resources/opaque-types/src/lib.rs" but somehow indirectly, it's hard to find the problem for one who is not aware of this "build-resources/opaque-types" component