openMSX 32bit support end - what are your thoughts?

Page 2/2
1 |

By Manuel

Ascended (17064)

Manuel's picture

28-10-2020, 09:51

Jepmsx, let me know what error you got and I will assist you.

By mcolom

Master (151)

mcolom's picture

28-10-2020, 09:53

jepmsx wrote:

Oh, I didn't know it was in flathub (https://flathub.org/apps/details/org.openmsx.openMSX). Great!

I tried to compile it in my Gentoo Linux machine without success. Knowing that there is a flatpak binary, I'll try it.

Probably you're missing some dependencies. You can run "sudo apt build-dep openmsx" at it should compile afterwards.
Good luck!

By gdx

Prophet (3813)

gdx's picture

28-10-2020, 10:06

What is the advantage of removing the 32bit support?

By Manuel

Ascended (17064)

Manuel's picture

28-10-2020, 10:06

mcolom wrote:
jepmsx wrote:

I tried to compile it in my Gentoo Linux machine without success. Knowing that there is a flatpak binary, I'll try it.

Probably you're missing some dependencies. You can run "sudo apt build-dep openmsx" at it should compile afterwards.
Good luck!

If your distro has 0.15.0 that won't be enough, as openMSX 16.0 is built on SDL2 and previous versions on SDL1.
Moreover, I don't think Gentoo uses APT Smile

By mcolom

Master (151)

mcolom's picture

28-10-2020, 10:21

Manuel wrote:

If your distro has 0.15.0 that won't be enough, as openMSX 16.0 is built on SDL2 and previous versions on SDL1.
Moreover, I don't think Gentoo uses APT Smile

Ah, didn't know about that. Actually it always worked for me with that, since in Debian testing is 16.0-1.
About apt, I saw that it can also be used in Gentoo, but indeed its better to use its standard package manager.
Anyway, I'm also available to help with jepmsx's compilation!

By sd_snatcher

Prophet (3366)

sd_snatcher's picture

28-10-2020, 11:54

I still have a C2D 2.3GHz machine running win10/32bit as HTPC/legacy win32 App support (*1) on my TV room. I wouldn't be able to run openMSX there anymore though.

That machine has an older BIOS that doesn't allow it to support 64bit windows. Anyway, I also use it for (*1).

*1: Some legacy dev apps are a pain to run, or just require drivers that don't run on 64bit, like the EPROM burner software.

By jepmsx

Resident (44)

jepmsx's picture

29-10-2020, 09:06

Thanks Manuel, I contact you in private to avoid polluting the page with compiling verbose

By jepmsx

Resident (44)

jepmsx's picture

30-10-2020, 09:42

I've compiled it successfully, the problem was to define CXX in the compilation. I've had to do make CXX=g++ and it's has compiled.

Thanks Manuel!

And thanks also to mcolom for your offer, I've realized it now.

Regarding 32bits support, I think that if it's troublesome to maintain I would drop it. The machines that are running old software can still use version 0.15 that works well.

By FiXato

Scribe (1635)

FiXato's picture

30-10-2020, 12:15

jepmsx wrote:

Regarding 32bits support, I think that if it's troublesome to maintain I would drop it. The machines that are running old software can still use version 0.15 that works well.

or they can build it themselves. Smile If I understand Vampier correctly, all he's saying is that he wants to stop building and providing the 32-bits builds himself.

Of course, it does mean that if there are 32-bits specific issues, they will be less likely to be identified early on, but in general it shouldn't prevent people from making 32-bits Windows builds themselves.

Page 2/2
1 |