Fix: ASM test compilation when binaries are missing

basics/checking-accounts/asm/Cargo.toml

@@ -1,4 +1,5 @@
 [package]
+build = "build.rs"
 name = "checking-account-asm-program"
 version = "0.1.0"
 edition = "2021"

basics/checking-accounts/asm/build.rs

@@ -0,0 +1,22 @@
+// The tests embed the assembled program with include_bytes!, which needs the
+// file to exist at compile time. `sbpf build` produces it, and it is gitignored,
+// so a fresh checkout has no binary and the test module cannot compile. Set a
+// cfg when the binary is present and let the tests key off it: present, they
+// compile and run; absent, they are left out and the crate still builds.
+use std::path::Path;
+
+const BINARY: &str = "deploy/checking-account-asm-program.so";
+
+fn main() {
+    // Declare the cfg so `-D warnings` builds do not fail on unexpected_cfgs.
+    println!("cargo::rustc-check-cfg=cfg(has_asm_binary)");
+    // Re-run when the binary appears or changes, so the cfg never goes stale.
+    println!("cargo::rerun-if-changed={BINARY}");
+
+    if Path::new(BINARY).exists() {
+        println!("cargo::rustc-cfg=has_asm_binary");
+    } else {
+        println!("cargo::warning=ASM binary not found at {BINARY}: tests skipped");
+        println!("cargo::warning=Run `sbpf build` in this directory to generate it");
+    }
+}

basics/checking-accounts/asm/src/lib.rs

@@ -1,4 +1,4 @@
-#[cfg(test)]
+#[cfg(all(test, has_asm_binary))]
 mod tests {
 
     use litesvm::LiteSVM;

basics/create-account/asm/Cargo.toml

@@ -1,4 +1,5 @@
 [package]
+build = "build.rs"
 name = "create-account-asm-program"
 version = "0.1.0"
 edition = "2021"

basics/create-account/asm/build.rs

@@ -0,0 +1,22 @@
+// The tests embed the assembled program with include_bytes!, which needs the
+// file to exist at compile time. `sbpf build` produces it, and it is gitignored,
+// so a fresh checkout has no binary and the test module cannot compile. Set a
+// cfg when the binary is present and let the tests key off it: present, they
+// compile and run; absent, they are left out and the crate still builds.
+use std::path::Path;
+
+const BINARY: &str = "deploy/create-account-asm-program.so";
+
+fn main() {
+    // Declare the cfg so `-D warnings` builds do not fail on unexpected_cfgs.
+    println!("cargo::rustc-check-cfg=cfg(has_asm_binary)");
+    // Re-run when the binary appears or changes, so the cfg never goes stale.
+    println!("cargo::rerun-if-changed={BINARY}");
+
+    if Path::new(BINARY).exists() {
+        println!("cargo::rustc-cfg=has_asm_binary");
+    } else {
+        println!("cargo::warning=ASM binary not found at {BINARY}: tests skipped");
+        println!("cargo::warning=Run `sbpf build` in this directory to generate it");
+    }
+}

basics/create-account/asm/src/lib.rs

@@ -1,4 +1,4 @@
-#[cfg(test)]
+#[cfg(all(test, has_asm_binary))]
 mod tests {
 
     use litesvm::LiteSVM;

basics/hello-solana/asm/Cargo.toml

@@ -1,4 +1,5 @@
 [package]
+build = "build.rs"
 name = "hello-solana-asm-program"
 version = "0.1.0"
 edition = "2021"

basics/hello-solana/asm/build.rs

@@ -0,0 +1,22 @@
+// The tests embed the assembled program with include_bytes!, which needs the
+// file to exist at compile time. `sbpf build` produces it, and it is gitignored,
+// so a fresh checkout has no binary and the test module cannot compile. Set a
+// cfg when the binary is present and let the tests key off it: present, they
+// compile and run; absent, they are left out and the crate still builds.
+use std::path::Path;
+
+const BINARY: &str = "deploy/hello-solana-asm-program.so";
+
+fn main() {
+    // Declare the cfg so `-D warnings` builds do not fail on unexpected_cfgs.
+    println!("cargo::rustc-check-cfg=cfg(has_asm_binary)");
+    // Re-run when the binary appears or changes, so the cfg never goes stale.
+    println!("cargo::rerun-if-changed={BINARY}");
+
+    if Path::new(BINARY).exists() {
+        println!("cargo::rustc-cfg=has_asm_binary");
+    } else {
+        println!("cargo::warning=ASM binary not found at {BINARY}: tests skipped");
+        println!("cargo::warning=Run `sbpf build` in this directory to generate it");
+    }
+}

basics/hello-solana/asm/src/lib.rs

@@ -1,4 +1,4 @@
-#[cfg(test)]
+#[cfg(all(test, has_asm_binary))]
 mod tests {
     use litesvm::LiteSVM;
     use solana_instruction::{AccountMeta, Instruction};

basics/transfer-sol/asm/Cargo.toml

@@ -2,6 +2,7 @@
 name = "asm"
 version = "0.1.0"
 edition = "2021"
+build = "build.rs"
 
 [dependencies]
 

basics/transfer-sol/asm/build.rs

@@ -0,0 +1,22 @@
+// The tests embed the assembled program with include_bytes!, which needs the
+// file to exist at compile time. `sbpf build` produces it, and it is gitignored,
+// so a fresh checkout has no binary and the test module cannot compile. Set a
+// cfg when the binary is present and let the tests key off it: present, they
+// compile and run; absent, they are left out and the crate still builds.
+use std::path::Path;
+
+const BINARY: &str = "deploy/transfer-sol-cpi.so";
+
+fn main() {
+    // Declare the cfg so `-D warnings` builds do not fail on unexpected_cfgs.
+    println!("cargo::rustc-check-cfg=cfg(has_asm_binary)");
+    // Re-run when the binary appears or changes, so the cfg never goes stale.
+    println!("cargo::rerun-if-changed={BINARY}");
+
+    if Path::new(BINARY).exists() {
+        println!("cargo::rustc-cfg=has_asm_binary");
+    } else {
+        println!("cargo::warning=ASM binary not found at {BINARY}: tests skipped");
+        println!("cargo::warning=Run `sbpf build` in this directory to generate it");
+    }
+}

basics/transfer-sol/asm/src/lib.rs

@@ -1,4 +1,4 @@
-#[cfg(test)]
+#[cfg(all(test, has_asm_binary))]
 mod tests {
     use litesvm::LiteSVM;
     use solana_instruction::{AccountMeta, Instruction};