Re: Bootstrapping and updating cargo-depends.mk

[pin <voidpin%protonmail.com@localhost>]

On Wednesday, April 22nd, 2026 at 10:02 PM, Rhialto <rhialto%falu.nl@localhost> wrote:

> Anyway, I didn't manage to get the mupdf-sys module to not compile its
> included C code. I'm not even sure where it determines what to do. I
> would expect that if it can compile the C code, the prerequisites would
> be present for using the pre-compiled (pkgsrc) version too...

I don't know exactly what you are trying to do but, if you want it to use the pkgsrc version
you need to tell the rust compiler where to find it.

For example, in devel/cargo-c/Makefile I've commented out libgit2

[...]
RUST_REQ=	1.92.0
MAKE_ENV+=	OPENSSL_DIR=${BUILDLINK_PREFIX.openssl}
RUSTFLAGS+=	-C link-arg=${COMPILER_RPATH_FLAG}${BUILDLINK_PREFIX.openssl}/lib
#RUSTFLAGS+=	-C link-arg=${COMPILER_RPATH_FLAG}${BUILDLINK_PREFIX.libgit2}/lib

[...]
#.include "../../devel/libgit2/buildlink3.mk"
BUILDLINK_API_DEPENDS.openssl+=	openssl>=3.0
.include "../../security/openssl/buildlink3.mk"
.include "../../lang/rust/cargo.mk"
[...]

In this case, I want it to use the vendored version. Because there too often there are version
mismatches which cause build failures. The pkgsrc version and the vendored version need to match
exactly if you want to use it. Else, the build will fail.

Now, if you want the opposite you need to tell the rust compiler where to find mupdf.

All that said, I must say I didn't look at bookokrat to check if it would allow the use of 
native mupdf.

Regards