-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Integrate Rust into build process #101
Comments
I've manifested my destiny all over the crates.io namespace: https://crates.io/crates/notcurses now to actually write some bindings :D |
We're uploading and maintaining libnotcurses-sys, generated by |
Add a simple rust demo if nothing else. I'd like to see this in 1.3.0. |
|
* CMake: add USE_PANDOC, USE_DOXYGEN options #101 * README: mention rust * start integrating rust into build #101 * CMake: add USE_NETWORK option for cargo * Debian: build-dep on doxygen * rust: colloquy checks in Cargo.lock * extract NCKEY defines into their own include * colloquy: use clap to parse CLI args * CMake: unify option namespace * Python: update include path * Rust: fix up --frozen workings for -DUSE_NETWORK=off * CMake: abstract out colloquy a little * Sync direct.hh to the New Way
If we want to run the libnotcurses-sys and notcurses Rust builds in our process, we'll need pass them a pkg-config path, since libnotcurses-sys looks for it. |
We can just export |
We're now building as part of the main CMake =] |
I'd like people to be able to write notcurses programs in Rust. Hack up some nice bindings.
The text was updated successfully, but these errors were encountered: