fix: skip QMD bundle on Darwin
QMD currently pulls a native better-sqlite3 rebuild that fails on Garnix Darwin because node-gyp cannot find Xcode/CLT in the builder. Keep QMD bundled and checked on Linux, but omit it from Darwin packages until the QMD package is Darwin-cacheable. Tests: nix eval --accept-flake-config --json .#checks.aarch64-darwin --apply 'builtins.attrNames'; nix eval --accept-flake-config --json .#checks.x86_64-linux --apply 'builtins.attrNames'; nix build --accept-flake-config .#checks.aarch64-darwin.ci --no-link --print-build-logs
This commit is contained in:
parent
e93384082a
commit
ce0da31f81
13
flake.nix
13
flake.nix
@ -37,10 +37,7 @@
|
||||
{ };
|
||||
qmdPkgsFor =
|
||||
system:
|
||||
if qmd ? packages && builtins.hasAttr system qmd.packages then
|
||||
qmd.packages.${system}
|
||||
else
|
||||
{ };
|
||||
if qmd ? packages && builtins.hasAttr system qmd.packages then qmd.packages.${system} else { };
|
||||
overlay =
|
||||
final: prev:
|
||||
import ./nix/overlay.nix {
|
||||
@ -62,11 +59,13 @@
|
||||
};
|
||||
openclawToolPkgs = openclawToolPkgsFor system;
|
||||
qmdPkgs = qmdPkgsFor system;
|
||||
qmdPackage =
|
||||
if pkgs.stdenv.hostPlatform.isDarwin then null else qmdPkgs.qmd or qmdPkgs.default or null;
|
||||
packageSetStable = import ./nix/packages {
|
||||
pkgs = pkgs;
|
||||
sourceInfo = sourceInfoStable;
|
||||
openclawToolPkgs = openclawToolPkgs;
|
||||
qmdPackage = qmdPkgs.qmd or qmdPkgs.default or null;
|
||||
inherit qmdPackage;
|
||||
};
|
||||
in
|
||||
{
|
||||
@ -100,9 +99,11 @@
|
||||
gateway-smoke = pkgs.callPackage ./nix/checks/openclaw-gateway-smoke.nix {
|
||||
openclawGateway = packageSetStable.openclaw-gateway;
|
||||
};
|
||||
}
|
||||
// pkgs.lib.optionalAttrs (qmdPackage != null) {
|
||||
qmd-runtime = pkgs.callPackage ./nix/checks/openclaw-qmd-runtime.nix {
|
||||
openclawPackage = packageSetStable.openclaw;
|
||||
qmdPackage = qmdPkgs.qmd or qmdPkgs.default or null;
|
||||
inherit qmdPackage;
|
||||
};
|
||||
}
|
||||
// (
|
||||
|
||||
Loading…
Reference in New Issue
Block a user