Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
73 user(s) are online (51 user(s) are browsing Forums)

Members: 0
Guests: 73

more...

Support us!

Headlines

 
  Register To Post  

« 1 ... 74 75 76 (77)
Re: SDL2
Just popping in
Just popping in


See User information
@Capehill understood. But just doing a plain make -f Makefile.amigaos4 will build which version? Ie, is there a flag to set for a specific version?

Go to top
Re: SDL2
Just can't stay away
Just can't stay away


See User information
@davec555

It tries to build MiniGL + Ogles2 + Mesa support by default.

Check build config and disable unwanted: https://github.com/AmigaPorts/SDL/blob ... DL_config_amigaos4.h#L357

Go to top
Re: SDL2
Just popping in
Just popping in


See User information
@Capehill I see you have this in the SDL_os4mesa.c file but don't see that define being used anywhere (and where you include the mesa includes). Can you tell me where that is? Just trying to get my head around it.

Thanks
Dave

Quote:

Something like this:

#ifdef USE_MESA_HEADERS
#include
#else
#include
#endif

For all relevant headers.

Go to top
Re: SDL2
Just can't stay away
Just can't stay away


See User information
@davec555

Basically following

#ifdef USE_MESA_HEADERS
#include <GL/Mesa/gl.h>
#else
#include <GL/MiniGL/gl.h>
#endif

is what I have in <GL/gl.h> and other GL headers.

Similarly for <GLES2/gl2.h>:

#ifdef USE_MESA_HEADERS
#include <GLES2/Mesa/gl2.h>
#else
#include <GLES2/Ogles2/gl2.h>
#endif

Go to top
Re: SDL2
Just popping in
Just popping in


See User information
@Capehill that explains it. Didn't even occur to me to actually look in the specific referenced includes themselves.
So in order for a thirdparty to compile it, they would need to create these custom headers, otherwise it just creates the minigl version only?

Thankyou!

Go to top
Re: SDL2
Just popping in
Just popping in


See User information
Good morning to all,

I've a question regarding SDL2 and the compositing renderer.

Why while using, for example, the sdl2benchmark application, while using the compositing renderer the SDL all the tests related to:
- FillRects
- RenderCopy
- RenderCopyEx
- Color Modulation

the window content is completely black?

The corresponding tests with software renderer works as expected.

Infact, if I select "compositing" as renderer in the SDL2prefs, all the SDL2 window application stays black.

QEMU emulator version 11.0.2
Pegasos2 - AmigaOS 4.1 FE Update 3
Go to top
Re: SDL2
Just can't stay away
Just can't stay away


See User information
@Kirirur

If you use an emulator which doesn't support compositing, then compositing renderer doesn't work. You need PatchCompositeTags for that.

Go to top
Re: SDL2
Just popping in
Just popping in


See User information
@Capehill

Hello, thank you for your hint. I'm currently using QEMU both on Linux MINT e macOS.

I'll try the patch you posted, even if the readme talks about WinUAE.

EDIT: just tried the patch on QEMU+Linux and after I launched it, not only the workbench crashed but also the X Server, I've to close it with Ctrl+Alt+Backspace.

I'm using https://github.com/derfsss/VirtIOGPU as my graphics card since it support 32 bit instead of 16 bit like sm501.

EDIT II: tested also with sm501: it does not crash, but the windows of the Workbench, for example, are missing the top border.


Edited by Kirirur on 2026/9/12 16:52:05
QEMU emulator version 11.0.2
Pegasos2 - AmigaOS 4.1 FE Update 3
Go to top
Re: SDL2
Quite a regular
Quite a regular


See User information
@Kirirur
Use the ATI driver for QEMU by BALATON Zoltan; “PatchCompositeTags” should work in 32-bit mode.
https://zero.eik.bme.hu/~balaton/qemu/ ... ti-vga-driver-latest.html
Don’t expect miracles.
The ATI driver by BALATON Zoltan alone will definitely work better for you than @derfsss’s VirtIOGPU.
VirtIOGPU uses a running flush process (this virtio-gpu implementation requires it—it’s not a bug by @derfsss) that consumes a lot of CPU on the guest side.
It would be possible to implement full compositing, but that’s completely pointless when the flush process itself on the AmigaOS4 side would consume 30–40% of the CPU.
Take a look here—you’ll find a benchmark of empty functions at https://hdrlab.org.nz/benchmark/gfxbench2d/os/amigaos/Result/3056, in the “Composite Score” section.
I don’t know how @Hans’s (A-EON) driver works. It might work with IGFX_COMPOSITETAGLIST_OFFSET set to 804 or 806, but if it operates on the same principle—with the flush process consuming CPU resources—then it’s definitely better to use BALATON Zoltan’s ATI driver for QEMU.

Go to top

  Register To Post
« 1 ... 74 75 76 (77)

 




Currently Active Users Viewing This Thread: 2 ( 0 members and 2 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2024 The XOOPS Project