On Tue, Mar 04, 2025 at 07:53:13PM GMT, Lydia Sobot wrote: > >> I was thinking more like a static library that is only used as a build > >> dependency but I'm not sure if that is possible in rust. > > > > It's not. Welcome to the standard ecosystem for modern languages! > Dumb question but what about the vendored dependencies available on the > release page? It could be completely useless here as I could have > misunderstood the problem, but I figured it may have been put up there > for a reason
My idea was that smithay could be a separate port so that when in the future we have multiple consumers they would not have to rebuild the whole thing each time. Apparently that isn't easily doable but it also isn't strictly necessary, I was just wondering if we could save some cycles. Regarding the vendored deps on the release page those don't work yet because I needed to patch a few of them. Our ports framework actually has some magic to solve most of the vendoring (see cargo-module(5)) but it only handles crates.io dependencies. Anything with an explicit git url doesn't work out of the box, that's why I download those manually in the included Makefile. > > Also, where are the portal configuration files, and why the launch > wrapper? I am not sure if anything portal related works on OpenBSD at this point so I chose not to include them. Maybe someone can correct me on that if they do actually make sense to ship (cc aja@) The launch wrapper makes sure XDG_RUNTIME_DIR is configured and exists. That isn't currently done automatically in OpenBSD. Most of it is copy-pasted from the sway port, see: https://github.com/openbsd/ports/blob/master/wayland/sway/files/startsway.sh > > Great to see this being added to OpenBSD in any case, I use it as my > daily driver but only have a headless OpenBSD box currently and > therefore dealt with packaging it only on other operating systems
