build: bump tools/rust_api to package the single-file header script - #1081
Conversation
|
@adsharma Thanks for merging this! Since 0.21.1 was cut just before it, the published crate still can't build from source. Would it be possible to cut a 0.21.2 when you get a chance? Happy to help test it. |
|
@kory-io if you're building from source why not build from ladybug-rust git repo? |
|
Thanks @adsharma! We did try that. A git dependency on ladybug-rust alone doesn't include the C++ sources ( For now we're building against a v0.21.1 checkout with |
Problem
lbug0.21.1 on crates.io still can't be built from source (LBUG_BUILD_FROM_SOURCE=1):The fix was merged in LadybugDB/ladybug-rust#43 (
28aba1c4). The crate is packaged from this repo'stools/rust_apisubmodule, though, which is still pinned atca706e51, one commit before the fix. So 0.21.0, 0.21.0-pre.20260929 and 0.21.1 all ship the oldincludelist:build.rsturnsBUILD_SINGLE_FILE_HEADERon, butlbug-src/scripts/collect-single-file-header.pyandheaders.txtaren't in the package.Fix
Bump
tools/rust_apifromca706e51to28aba1c4. That commit's only change is the packaging fix: the two script files are added topackage.include, with matchingrerun-if-changedlines.Verification
28aba1c4withLBUG_BUILD_FROM_SOURCE=1 cargo packagesucceeds. Cargo's verification step builds the tarball from source and generateslbug.hpp(shown in build: package the single-file header script for source builds ladybug-rust#43).A 0.21.2 from this commit would let crates that build from source use 0.21.