Open rodarima opened 9 months ago
I will continue the discussion here, as the other PR was for OpenSSL 1.1 support only.
Do you see any messages in the terminal?
There are no error messages, it just times out after some time with the message
Dns_server [0]: <hostname> is (nil)
But seems to be a bit random. Sometimes it works. Maybe just a problem with my setup (using aranym with a bridge to the host), since sometimes other network connections also fail. I've always used --disable-threaded-dns, since the only thread implementation currently available is pth, and that is non-preemptive and just causes problems because of this.
That's strange, but if you report that other network connections fail maybe is not related with Dillo.
Adding /usr/local/include is required in some BSD systems
I have disabled that currently when using gcc, since gcc should always look in that directories by default. Should that cause problems on BSD system, the test could also be changed to
if test "$cross_compiling" = no
Other things that i changed: looking for png library uses png-config. I've tested it also on linux, but may need some testing for other systems.
For FLTK i currently just use -lfltk when cross-compiling, since it does not seem to require any special cflags. Maybe that test could also be changed to some
AC_CHECK_LIB
.The dpi programs have to be linked explicitly to the x11 libraries. This is again only needed because of static libraries, but should not hurt on other systems.
Searching for openssl also uses pkg-config now. I have no mbedtls yet, so i don't know what files are installed there.
All in all the patches aren't that large, so if you don't want to apply them, i can just keep them as mint-specific patches.
But note that this is all quite experimental. There are other quirks currently, some drawing problems (which i suspect to be fVDI problems in combination with aranym), the tooltips sometimes immediately disappearing again etc. And of course that X.App that is needed is also quite experimental.
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.
However the rendering always is quite strange, also in the linux version of dillo. Maybe some features of CSS that are not implemented yet?
Yeah, the support for CSS is not complete (yet).
Thanks for the patch!
Or I don't know how complicated is to setup the simulator for Atari.
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
Or I don't know how complicated is to setup the simulator for Atari.
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.
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:
For a working freemint environment, you should be able to use the snapshot builds of freemint: https://tho-otto.de/snapshots/freemint/bootable/
Which file(s) do I need exactly? And can you specify how to invoke ARAnyM to load the ROM/images?
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
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.
Managed to get EmuTOS loading:
But no idea how to load FreeMiNT.
Managed to boot FreeMiNT and open a bash shell:
It seems to be available in the AUR which builds it from: I'm guessing that may work (?). It asks for a ROM:
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)
Which file(s) do I need exactly? And can you specify how to invoke ARAnyM to load the ROM/images?
Seems you have figured that out already. You should specify EmuTOS as ROM in ~/.aranym/config
[GLOBAL]
EmuTOS = emutos-aranym.img
Managed to boot FreeMiNT and open a bash shell:
Nice. Thats almost all you need. Easiest way to access other files is to map a host filesystem:
[HOSTFS]
H = ~/
(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)
It seems to be available in the AUR which builds it from: I'm guessing that may work (?). It asks for a ROM:
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)
Okey, I'll adjust the PKGBUILD.
Which file(s) do I need exactly? And can you specify how to invoke ARAnyM to load the ROM/images?
Seems you have figured that out already. You should specify EmuTOS as ROM in
~/.aranym/config
[GLOBAL] EmuTOS = emutos-aranym.img
I'm using the runme.sh
insize freemint-1-19-bc6492f7-040-aranym.zip
, EmuTOS
is already set to that value.
Managed to boot FreeMiNT and open a bash shell:
Nice. Thats almost all you need. Easiest way to access other files is to map a host filesystem:
[HOSTFS] H = ~/
(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)
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: