Date: Wed, 24 Jan 2024 17:51:15 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Stefan =?utf-8?Q?E=C3=9Fer?= <se@FreeBSD.org> Cc: ports-committers@FreeBSD.org, dev-commits-ports-all@FreeBSD.org, dev-commits-ports-main@FreeBSD.org Subject: Re: git: eecf3562b01d - main - devel/jujutsu: fix install on other targets than amd64 Message-ID: <sf2m-isjg-wny@FreeBSD.org> In-Reply-To: <202401241532.40OFWS9b081933@gitrepo.freebsd.org> ("Stefan =?utf-8?Q?E=C3=9Fer=22's?= message of "Wed, 24 Jan 2024 15:32:28 GMT") References: <202401241532.40OFWS9b081933@gitrepo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Stefan E=C3=9Fer <se@FreeBSD.org> writes: > I'd appreciate any hint regarding a better way to install this program > to the stage directory than the hacked do-install target I use. https://cgit.freebsd.org/ports/commit/?id=3D4eab6d126148 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271358 According to "rg -l CARGO_INSTALL_PATH" there're 30 examples in the tree. For one, in games/veloren-weekly I use the following: # XXX https://github.com/rust-lang/cargo/issues/4101 CARGO_INSTALL_PATH=3D server-cli voxygen ... do-install: # XXX [workspace.dependencies] breaks rebuild in subdirs .for f in ${CARGO_INSTALL_PATH} ${INSTALL_PROGRAM} ${CARGO_TARGET_DIR}/*/*/${PORTNAME}-$f \ ${STAGEDIR}${PREFIX}/bin .endfor > - ${INSTALL_PROGRAM} ${WRKDIR}/target/${__ARCH}/release/jj \ > + ${INSTALL_PROGRAM} ${WRKDIR}/target/*-unknown-freebsd/release/jj \ - Don't hardcode "freebsd" to avoid patching in DPorts (DragonFly) - Don't hardcode "release" as it'd break WITH_DEBUG=3D builds
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?sf2m-isjg-wny>