Index | Thread | Search

From:
yaydn@protonmail.com
Subject:
Re: new(ish) devel/sdl3
To:
Omar Polo <op@omarpolo.com>
Cc:
"ports@openbsd.org" <ports@openbsd.org>, "thfr@openbsd.org" <thfr@openbsd.org>
Date:
Fri, 01 Aug 2025 17:42:58 +0000

Download raw body.

Thread
På fredag 1. august 2025 kl. 17:36, Omar Polo
<op@omarpolo.com> skrev:

> Stuart Henderson stu@spacehopper.org wrote:
>
> > On 2025/08/01 11:06, Omar Polo wrote:
> >
> > > Stuart Henderson stu@spacehopper.org wrote:
> > >
> > > > On 2025/07/31 17:46, Omar Polo wrote:
> > > > [...]
> > > > these wantlib changes I think are already there (i'm a bit confused by
> > > > love and why it picks up those libraries tbf) but since they don't
> > > > mention sdl3 I guess they're unrelated.
> >
> > yes, unrelated. they come from some other library depended on by thise
> > ports, which started pulling in those additional libraries. some are
> > a little problematic as they're arch-dependent e.g. drm_intel is only
> > on i386/amd64, LLVM.9 only on base-gcc archs, and we don't have a good
> > way to deal with that. (iconv is due to iirc a change in gettext).
> >
> > I synced up some of these recently (concentrating on ports where
> > packages were totally broken due to no LIB_DEPENDS chain to a library
> > they needed, and missing base libs - c/pthread) but there are bunch left.
>
>
> gotcha
>
> > The port that I remembered preemptively disabling sdl3 (until ready to
> > change) was fluidsynth, btw.
> >
> > > Regarding the wayland thing, I don't have a strong opinion. I just took
> > > thfr@ port since I needed to try updating and debugging an issue with
> > > lto in games/taisei. I haven't looked yet into (what kind of pain)
> > > enabling wayland support is.
> >
> > tbh I think it's a bit of a distraction and it won't cause issues to
> > punt it to later. the important thing is to make sure it is either
> > explicitly disabled or enabled and not let it autodetect because that
> > will break bulk builds during junking (and some of the wayland-related
> > ports are header only so are hard to detect; port-lib-depends-check
> > won't help for wayland-protocols for example).
>
>
> Since I got asked again, here's a version of the port with wayland
> enabled. I haven't tested it (yet?)


Tested this version on current/amd64. Built and looks good.

Think this is a typo:

			-DSDL_WAYLAND=OON \

'OON' instead of 'ON'. It enabled even so. ¯\_(ツ)_/¯

Also for alphabetical order in LIB_DEPENDS, if important, would be:

			wayland/wayland \
			x11/xkbcommon

I think.

Thank you again.

>
> The test that is crashing is due to some missing joystick support that
> maybe we can do without for now.
>
> 08/01/25 17:18:22: ----- Test Case 7.1: 'TestVirtualJoystick' started
> 08/01/25 17:18:22: Test Description: 'Test virtual joystick functionality'
> 08/01/25 17:18:22: Test Iteration 1: execKey 16048902390838107396
> 08/01/25 17:18:22: Assert 'SDL_InitSubSystem(SDL_INIT_GAMEPAD)': Passed
> ERROR: 08/01/25 17:18:22: Assert 'SDL_AttachVirtualJoystick() -> 0 (expected > 0)': Failed
>
> ERROR: 08/01/25 17:18:22: Assert 'SDL_IsJoystickVirtual()': Failed
> 08/01/25 17:18:22: Assert '!SDL_IsJoystickVirtual()': Passed
> ERROR: 08/01/25 17:18:22: Assert Summary: Total=4 Passed=2 Failed=2
> 08/01/25 17:18:22: Total Test runtime: 0.0 sec
>
> I'm also going to send the taisei update that depends on this if people
> want to test it.


Yes please.

Have a good one and well wishes.