Crates.io | bitnet-cpp-sys |
lib.rs | bitnet-cpp-sys |
version | 0.0.4 |
source | src |
created_at | 2024-10-25 23:12:11.094192 |
updated_at | 2024-11-17 12:07:16.053843 |
description | Low Level Bindings to bitnet.cpp |
homepage | |
repository | https://github.com/eugenehp/bitnet-cpp-rs |
max_upload_size | |
id | 1423382 |
size | 8,310,819 |
Raw bindings to bitnet.cpp.
See bitnet-cpp for a safe API.
Atomic git patches are incorporated into the build.rs
, but if you want to dive deeper, see the patch generation below.
cargo clean && cargo build
Apply patches from the python generation:
./patches/apply.sh
Generate python changes:
cd bitnet
pip install -r requirements.txt
python setup_env.py --hf-repo HF1BitLLM/Llama3-8B-1.58-100B-tokens -q i2_s
Create patches after you're done generating python changes:
./patches/create.sh
Clean git commits from submodules to start over or run commits:
./patches/clean.sh
# this won't build without cleaning first, though normal cargo build works as is.
cargo clean && BUILD_DEBUG=true CMAKE_VERBOSE=true cargo build
Check which files will be included in the published crate:
cargo package --list --allow-dirty
Do a dry run:
cargo publish --allow-dirty --dry-run
Or you can simply remove bitnet/3rdparty/llama.cpp/common/build-info.cpp
and run:
cargo publish --dry-run
© 2024, Eugene Hauptmann