about summary refs log tree commit diff
path: root/test/python/server_test_case.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-11-06 16:39:09 +0000
committerpjotr <pjotr.public01@thebird.nl>2026-11-06 16:59:53 +0000
commit485531c9cf2185e81ba27509dec8ac96467feb21 (patch)
treebe8f14e1e6ef30a0c5804db47e5af34b16cf707c /test/python/server_test_case.py
parent108b2e13925a5ab040635a96d6c920d023b0bbad (diff)
downloadgenenetwork4-485531c9cf2185e81ba27509dec8ac96467feb21.tar.gz
guix: pin Xapian 1.4.29, document the dependency-shell build
The xapian-rs git revision Cargo.toml pins was written against Xapian
1.4: it generates bindings for Xapian::InMemory::open, which Xapian 2.0
removed (2.x spells it as the Xapian::DB_BACKEND_INMEMORY flag), and
autocxx then aborts with "the 'generate' or 'generate_pod' directive for
'Xapian::InMemory::open' did not result in any code being generated".
2.x's headers also need C++17, where autocxx hands the parser a fixed
-std=c++14 that 1.4's headers accept.  Guix's own xapian has moved to
2.1.0, so guix build -f guix.scm stopped working; pin the last 1.4
release instead of tracking it.

* guix.scm (xapian-1.4): new variable, Xapian 1.4.29 inheriting
xapian's inputs, with 1.4's own check targets.
(genenetwork4-git)[inputs]: use xapian-1.4.
(use-modules): (guix download), for url-fetch.
* README.md (Running with cargo): "Building with cargo, outside a bare
toolchain", the guix shell -D variables that a bare cargo build lacks.
(Running with Guix): why xapian is pinned, and when to drop it.
Diffstat (limited to 'test/python/server_test_case.py')
0 files changed, 0 insertions, 0 deletions