v0.10.1: resolve vorbis shim -include against package dir
v0.10.0's compile-c-sources for the vendored vorbis tree used a literal relative -include vendor/vorbis/sigil_alloca_shim.h. That resolves correctly when sigil-audio itself is the working directory (how the vendoring worker verified), but breaks the moment a downstream consumer (live-crafter, cinder-cantata, anything via sigil deps) tries to compile sigil-audio's C — the cc invocation runs from a different cwd and can't find the shim header.
Fix: switch the flags list to a procedural form that resolves the shim path against (context-package-dir ctx) at build time. Same file, same cross-compile logic; just a path that works from any cwd.
Surfaced 2026-04-24 when live-crafter's first post-v0.10.0 build failed with "'vendor/vorbis/sigilallocashim.h' file not found" after the sigil-audio pin bumped to ^0.10.0.
package.sgl | 22 +++++++++++++++-------
1 file changed, 15 insertions(+), 7 deletions(-)package.sglmodified
;; needs it for the alloca prototype under -std=c99) but ;; NOT on Windows/MinGW (where <alloca.h> is missing and ;; vorbis's _WIN32 branch handles alloca via <malloc.h>). flags: '("-std=c99" "-include" "vendor/vorbis/sigil_alloca_shim.h" "-Wno-parentheses" "-Wno-unused-function" "-Wno-unused-but-set-variable" "-Wno-sign-compare" "-Wno-strict-aliasing")) ;; ;; Flags are procedural so the -include path is resolved ;; against this package's own directory. Literal relative ;; paths would break downstream consumers whose cwd differs ;; from the package dir at cc time. flags: (lambda (ctx) (list "-std=c99" "-include" (path-join (context-package-dir ctx) "vendor/vorbis/sigil_alloca_shim.h") "-Wno-parentheses" "-Wno-unused-function" "-Wno-unused-but-set-variable" "-Wno-sign-compare" "-Wno-strict-aliasing"))) ;; sigil-audio's own C sources. (compile-c-sources