[openMSX] Windows development builds

Page 2/2
1 |

By ren

Paragon (1521)

ren's picture

20-09-2020, 16:43

Thanks, working well here! (package from fixato.net)

@Bodhi: as Vampier only provides the openmsx executables: you did try to run it inside an existing fully deployed (v16) directory?

@Manuel: ever considered the option/possibility to distribute openMSX as a Flatpack (or similar) app?

By Bodhi1969

Expert (70)

Bodhi1969's picture

20-09-2020, 16:56

Manuel wrote:

[...]And still, I would recommend to use a native Linux binary (you should be able to build it yourself, but if you need help, do let me know), although openMSX runs pretty well with Wine.

Well, I´am a bit uncertain / scary about compiling OpenMSX because as I understand it Catapult and OpenMSX have to be compiled separatly. I don´t know how to combine them at the end. That´s why I use the latest Windows-Build under Wine and just tried out the latest vampir-build-executable, whereas tho one from today gave out a bunch of error messages I don´t recall and the one from 2020-09-14 works as it should here.

By Bodhi1969

Expert (70)

Bodhi1969's picture

20-09-2020, 16:57

ren wrote:

Thanks, working well here! (package from fixato.net)

@Bodhi: as Vampier only provides the openmsx executables: you did try to run it inside an existing fully deployed (v16) directory?

Sure, just replaced the executables.

By Manuel

Ascended (16961)

Manuel's picture

20-09-2020, 17:04

Only get development builds from http://openmsx.dev/ These are consistent.

When compiling yourself, you don't need to combine Catapult and openMSX. When you start up Catapult and it can't find openMSX on the default location, you can set up the proper location. That's all it needs.

By Manuel

Ascended (16961)

Manuel's picture

20-09-2020, 17:05

ren wrote:

@Manuel: ever considered the option/possibility to distribute openMSX as a Flatpack (or similar) app?

As usual, pull requests are welcome.

By ren

Paragon (1521)

ren's picture

20-10-2020, 11:13

Page 2/2
1 |