2.32.56
This is a stable bugfix release, with the following changes:
Fixed rendering in Mesen2
Fixed brightness in ioquake3
Fixed a hang at launch in the xemu emulator
Fixed crackling and sped up audio in OpenRCT2
Fixed fullscreen window positioning on Wayland with multiple displays
Key events are now sent for dead keys on X11
Fixed mouse wheel integer scrolling values
Fixed a double-free when working with RLE surfaces
Fixed a memory leak in SDL_LockTextureToSurface()
Fixed sending SDL3 controller events to SDL2 applications
2.32.54
This is a stable bugfix release, with the following changes:
sdl2_compat.pc was renamed to sdl2-compat.pc
Fixed creating fullscreen exclusive windows
Fixed relative mouse motion for Half-Life and mods on Windows
Fixed crash during controller hotplug in RetroArch
Fixed display scale under Wayland in ioquake3
Default to using X11 for the UE5 editor, fixing mouse input
Fixed SDL_SetWindowInputFocus() return value
Improved accuracy of SDL_GetRenderDriverInfo()
Improved handling of very slight mouse movements
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com