Preconfigured emulators for game distribution

[Dbug]

Hi,
I've successfully setup Oricutron to be easy to run on Windows with a game, and I was wondering how difficult it would be to do the same for Linux, Mac, iOS or Android.

Here for example what that looks like for Space: 1999

[iss]

There is a BIG file: 'images/gfx_atmoskbd.psd' - it's unused and can be removed.
I'm sure it can be done easy for macOS and Android.
For Linux there should be a way like 'appimage' or 'flatpack', unfortunately simple compiled on (for instance latest) Fedora doesn't run on Ubuntu (of course the CPU is the same x86_64).
For iOS - I don't know, I think nobody tried ever compile it...

[Dbug]

There is a BIG file: 'images/gfx_atmoskbd.psd' - it's unused and can be removed.

Good catch!

I'm sure it can be done easy for macOS and Android.

Can standard Android run APK files, or does it need to be jailbreaked?

For Linux there should be a way like 'appimage' or 'flatpack', unfortunately simple compiled on (for instance latest) Fedora doesn't run on Ubuntu (of course the CPU is the same x86_64).
For iOS - I don't know, I think nobody tried ever compile it...

Ok

[iss]

...
Can standard Android run APK files, or does it need to be jailbreaked?

The APK is just packed file for distribution, so it need to be "installed" on the device.
There should be no problem to run Oricutron on any android device.

[ibisum]

Do you mean ready-to-run packages for each system?

The Makefile has a few package-PLATFORM targets, where PLATFORM is one of a variety of Linux/Mac- specific build scripts, constructing pretty *rudimentary* app bundles for each target ("packaging"), but these could probably use a bit of work, if the intention is to be able to build Oricutron into an App-branded/-specific bundle? There could be a Debian-style .deb target added relatively easy, etc.

But on the subject of making Oricutron a sub-module to a publishable App Bundle .. I'm not sure how I'd feel about that as a long-time Oricutron user, though .. is this License-compliant?

Surely its better to have the web build being used to give the 'easy to just play' use case to users on the Internet, but leave Oricutron itself relatively unencumbered by lock-down in an app-store context? The Web target for Oricutron works pretty well, you know ..

[Dbug]

Do you mean ready-to-run packages for each system?

Ready to run game: Download and play.

Surely its better to have the web build being used to give the 'easy to just play' use case to users on the Internet, but leave Oricutron itself relatively unencumbered by lock-down in an app-store context? The Web target for Oricutron works pretty well, you know ..

Performance wise, how does it compare with a natively compiled Oricutron? (thinking of low power devices)
Does it run 100% well on both Chromium and Firefox?

[ibisum]

The oricutron repo as of git commit 256bf6a contains all you need to build the web target .. but its not (yet) a distinct target in the main Makefile, as it requires a bit of resource management that isn't automated .. so you've got to use the build rig that is in the www/ directory, and check the Readme.txt for details on how to build the web version.

Performance- and compatability- wise, whatever you find, I'll try to help fix and I'm sure iss and the other contributors of the web front-end work will be happy to see us push things further too ..

[Dbug]

For web Oricutron, maybe continue on the existing thread

[ibisum]

Yup, good idea.

Psst, already mentioned this elsewhere, but you should include a link to the Oricutron sources alongside the binary downloads, *ahem* *cough* *cough* .. GPLv2 .. *cough* ..

[Dbug]

Yup, good idea.

Psst, already mentioned this elsewhere, but you should include a link to the Oricutron sources alongside the binary downloads, *ahem* *cough* *cough* .. GPLv2 .. *cough* ..

I did not make the Oricutron package, and as far as I can see, there's no mention of any form of licence or link to where the versions are available, and where the source code is present.

Maybe from now on the Oricutron archives should have this information in one of the text files:
- Where the latest binaries are located (https://raxiss.com/article/id/25-Oricut ... Developers ?)
- Where the latest source code is located (https://github.com/pete-gordon/oricutron ?)
- What the licence is

While on the topic, it's actually difficult to know where the binary releases are, because https://github.com/pete-gordon/oricutron/releases does not have any content, and the main readme does not say anything about https://raxiss.com/article/id/25-Oricut ... Developers

[ibisum]

I think the point is, you can build and release your own binaries derived from the Oricutron source files, and thats what folks in your example have done. Its perfectly okay to do your own build - and in your case, for itch.io, it'd be fantastic to get the web target working sufficiently well to the task.

But there still has to be a link included to the sources for the Oricutron program, alongside the binary links.

The use of the GPLv2License is expressed in each of the source files - and this is also expressed in the "About.." menu option of Oricutron, incidentally, so you can see an example of the URL to use ... which is indeed https://github.com/pete-gordon/oricutron as you've found.

Yes, we should encourage Peter to put a LICENSE.txt in the root of the repo, I will make the administrivia for that right now .. (edit:
https://github.com/pete-gordon/oricutron/pull/197)

[Dbug]

I think the point is, you can build and release your own binaries derived from the Oricutron source files, and thats what folks in your example have done.

And my point is that I don't want to build my own version.

The reason Dungeon Master, Encounter, Quantum FX, ... have not been released is that I spent my life working on the website, blog, documentation, OSDK, helping people, etc...

I don't want to also build my own version of the emulator: I do not have the time or the will to do that.

[ibisum]

Oh, I mistakenly thought you were doing your own builds.

In that case, whoever you got the build from, should have also provided a link to the sources as well.

Anyway .. maybe we should talk about this build issue of yours. I now think about adding Github actions to build 'official packages' as a contribution, in which case it would just be a matter of downloading the official binaries, adding your content, and leaving it at that.

I'll have time for a proper session over the next few days. There should be an easy target to build the web front end now that Iss and the gang have done all the hard work, I can take the scaffolding down and sweep up the street a bit, so to speak. Do you foresee the ability to add a web package build of Oricutron to your itch.io profile as being a useful target? Or are you looking at charging for the downloads at itch.io as more of a necessary goal?

[iss]

... I now think about adding Github actions to build 'official packages' as a contribution, in which case it would just be a matter of downloading the official binaries, adding your content, and leaving it at that.

This will be really useful!

[Dbug]

Automated publishes with all the necessary licence/information directly on the GitHub page seems like something very good.

Do you foresee the ability to add a web package build of Oricutron to your itch.io profile as being a useful target? Or are you looking at charging for the downloads at itch.io as more of a necessary goal?

Easily adding playable web versions on all the old free games seem like totally worth it.

Regarding Encounter, my current idea is to have the game for free for the people who download it from Defence Force, and try to sell the game at a small price on itch.io (as an experiment mostly: Would people pay for retro games for the Oric).

But even if it was for pay, would still be good to have a playable demo directly in the browser