rebuild on tar file change (#163)

* rebuild on tar file change * run examples
duckdb · May 21, 2023 · f6028d9 · f6028d9
1 parent cfda58b
commit f6028d9
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/.github/workflows/rust.yaml b/.github/workflows/rust.yaml
@@ -147,8 +147,8 @@ jobs:
           # as the other tests have them.
           RUST_BACKTRACE: "0"
         run: cargo -Z build-std test --features "modern-full extensions-full" --target x86_64-unknown-linux-gnu
-      - name: Build loadable extension
-        run: cargo build --example hello-ext --features="vtab-loadable bundled"
+      - run: cargo install cargo-examples
+      - run: cargo examples --skip hello-ext --features=bundled
       - uses: wangfenjin/publish-crates@main
         name: cargo publish --dry-run
         with:

diff --git a/libduckdb-sys/build.rs b/libduckdb-sys/build.rs
@@ -134,6 +134,8 @@ mod build_bundled {
         // Since the manifest controls the set of files, we require it to be changed to know whether
         // to rebuild the project
         println!("cargo:rerun-if-changed={}/manifest.json", lib_name);
+        // Make sure to rebuild the project if tar file changed
+        println!("cargo:rerun-if-changed=duckdb.tar.gz");
 
         cfg.include(lib_name);