From: Stuart Henderson <stu@spacehopper.org>
Subject: Re: [NEW] devel/tomlplusplus
To: SASANO Takayoshi <uaa@mx5.nisiq.net>
Cc: ports@openbsd.org, Antoine Jacoutot <ajacoutot@bsdfrog.org>
Date: Tue, 23 Dec 2025 19:31:04 +0000

On 2025/11/29 11:13, SASANO Takayoshi wrote:
> Hello,
> 
> Here is the port of tomlplusplus(https://github.com/marzer/tomlplusplus).
> 
> This is required by Hyprcursor (https://github.com/hyprwm/hyprcursor),
> cursor library for Hyprland wayland compsitor.
> -- 
> SASANO Takayoshi (JG1UAA) <uaa@mx5.nisiq.net>
> 

This fails unless the build is run with the port in a directory which
is writable by the build user. (If this *doesnt't* fail, you are working
on ports with a dangerous setup).

Attached tgz fixes this by cd'ing to ${WRKSRC} before running configure,
though I wonder if meson.port.mk should do that? (cc'ing Antoine,
--system-information is used by mesonbuild/modules/cmake.py).

Index: meson.port.mk
===================================================================
RCS file: /cvs/ports/devel/meson/meson.port.mk,v
diff -u -p -r1.119 meson.port.mk
--- meson.port.mk	10 Dec 2025 17:44:14 -0000	1.119
+++ meson.port.mk	23 Dec 2025 19:23:05 -0000
@@ -58,7 +58,7 @@ MODMESON_post-patch=	@ln -sf /usr/bin/fa
 
 CONFIGURE_ARGS +=	${MODMESON_CONFIGURE_ARGS}
 CONFIGURE_ENV +=	${MODMESON_CONFIGURE_ENV}
-MODMESON_configure=	${SETENV} ${CONFIGURE_ENV} ${LOCALBASE}/bin/meson setup \
+MODMESON_configure=	cd ${WRKSRC}; ${SETENV} ${CONFIGURE_ENV} ${LOCALBASE}/bin/meson setup \
 				${CONFIGURE_ARGS} ${WRKSRC} ${WRKBUILD}
 
 .   if !target(do-build)

(Attached tgz also moves the category to textproc, tidies things
up around DISTNAME, uses a more generic WANTLIB and adds ports-gcc
to COMPILER, it builds ok there).