Nikita Ronja
Nikita Ronja
since nothing substantial changed in the cmake parts for 2 years, I guess you no longer use cmake for install but build.zig and something changed between 0.11 and 0.12 in...
using `CMAKE_CONFIGURE_ARGS+= -DCMAKE_INSTALL_PREFIX=${DESTDIR}${PREFIX}` doesn't change a thing in the outcome. I'd appreciate pointers in how/where to make zig install in our chroot build environment again.
I have to add: it works **outside** of a chroot without issues. I can safely build and install zig when I run it from pkgsrc as a user (make clean;...
We've changed nothing which would touch this (to my knowledge), that's why we're asking you what changed between 0.11 and 0.12 that we'd encounter this suddenly.
pbulk (or anything building) doesn't have write access to /usr/pkg. The builds of pkgsrc happen in ${WRKSRC}, which by default is ${WRKDIR}/${DISTNAME}. We write something like a binary named "zig"...
I am on irc, but I don't have enough time today. Tomorrow I'm available.
Not really a fix, but what if I packaged the zig-bootstrap, used that to build zig and see if we run into the same issue? `zig build` and builds+installs of...
A minimal working example with libhidapi 0.14.0 from pkgsrc gets me as far as this (while building the example in the post below), this seems to be picking up libusb1...
minimal example: cargo.toml ``` [package] name = "hello_world" # the name of the package version = "0.1.0" # the current version, obeying semver authors = ["Alice ", "Bob "] edition...