Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

This project needs capnproto and should mention it #104

Open
svenstaro opened this issue May 1, 2016 · 2 comments
Open

This project needs capnproto and should mention it #104

svenstaro opened this issue May 1, 2016 · 2 comments

Comments

@svenstaro
Copy link

When naively trying to build an example project, one gets this:

thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: Error { kind: Failed, description: "Error while trying to execute `capnp compile`: Failed: No such file or directory (os error 2).  Please verify that version 0.5.2 or higher of the capnp executable is installed on your system. See https://capnproto.org/install.html" }', src/libcore/result.rs:746
note: Run with `RUST_BACKTRACE=1` for a backtrace.

You should mention that you require capnproto to be installed in the system beforehand.
@ehiggs
Copy link

ehiggs commented Jun 9, 2016 •
edited

My understanding is that there should be a capnp-sys crate which builds capnproto and provides a thin ffi wrapper around it. The capnp crate should then add a 'rustic' API. This is the intended cargo use case since it means crates can be built with minimal requirements from the environment. iow, OS installed libraries are for the OS and system administration tools. Build system libraries are for applications so they can manage the dependencies with fine control.

@ehiggs ehiggs mentioned this issue Jun 9, 2016
Closed
@svenstaro
Copy link
Author

That would work.

@ehiggs ehiggs mentioned this issue Jun 6, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@svenstaro @ehiggs