-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Atari machines #34
Comments
I will continue the discussion here, as the other PR was for OpenSSL 1.1 support only.
That's strange, but if you report that other network connections fail maybe is not related with Dillo.
I think most of those patches can be included in Dillo. But I'll have to think a way to test it under CI, so I can avoid breaking it in the future. Maybe I can find a way to cross compile to ARM, which would exercise most of the cross compilation logic. Or I don't know how complicated is to setup the simulator for Atari.
Yeah, the support for CSS is not complete (yet). Thanks for the patch! |
Well first thing you would need is aranym ;) Unforunately, currently snapshots are still not available since bintray closed, so you have to compile it yourself. But it is autotools based, so shouldn't be that hard. For a working freemint environment, you should be able to use the snapshot builds of freemint: https://tho-otto.de/snapshots/freemint/bootable/ Getting network working is another thing though. Precompiled libraries for fltk, openssl and everything else you might need are available at https://tho-otto.de/crossmint.php |
It seems to be available in the AUR which builds it from: http://downloads.sourceforge.net/sourceforge/aranym/aranym_1.1.0.orig.tar.gz I'm guessing that may work (?). It asks for a ROM:
Which file(s) do I need exactly? And can you specify how to invoke ARAnyM to load the ROM/images?
Okay, I'll try that eventually. First, I'll try to setup a CI runner that does a cross compilation from x64 to something else (probably ARM) as that seems like an easier first step. Once that works, I see if I can try to boot ARAnyM myself and built it there. |
That might work, but there haven't been any releases for a while. You can use it as a start, but eventually you should replace that later by a freshly compiled version from the source repo (https://github.com/aranym/aranym)
Seems you have figured that out already. You should specify EmuTOS as ROM in
Nice. Thats almost all you need. Easiest way to access other files is to map a host filesystem:
(or some other dir) Edit: You should make sure that important directories like /usr point to a filesystem that supports long filenames, otherwise you run into trouble with lots of unix programs. /usr is typically setup as a symlink in u:\usr (U:\ is the root filesystem for MiNT) |
Okey, I'll adjust the PKGBUILD.
I'm using the
So you cross-compile Dillo with dynamic libs and then you share the binary and dependencies inside the VM with the HOSTFS mounts? |
There aren't any dynamic libs ;) But basically yes, i cross-compile dillo on linux, then switch to aranym, cd to the directory where i just compiled it on the host, and run it from there. For the dip-programs, you can copy them inside aranym to the /usr/lib/dillo directory. But i think for a first test they are not needed. But it seems it is not that easy to setup the X.app for atari correctly. See also the thread https://www.atari-forum.com/viewtopic.php?p=455548#p455548 |
Following this thread:
https://www.atari-forum.com/viewtopic.php?t=43326
The folks at Atari Forum managed to get Dillo working on an Atari simulator:
I'm opening this issue to track the current status of the port and to see what changes we may need to add to Dillo and the build system to improve the support for this platform.
Some of the issues and quirks required are discussed in #33. Most of them are caused by the not great support for cross compilation.
Here is the that @th-otto provided to build it on this platform. It needs to cross-compile Dillo using the
m68k-atari-mint-g++
compiler:The text was updated successfully, but these errors were encountered: