May 15th, 2011 by Moggen

AROS built as hosted in Linux with X11 needs the “Backingstore” enabled to work properly.

This can be done by creating the file /usr/share/X11/xorg.conf.d/05-backingstore.conf and putting this into it:

Section "Device"
        Identifier "Default device"
        Option "Backingstore"
EndSection

This works for my Ubuntu running inside a VirtualBox machine. If you are running Linux natively, you will probably want to edit the Device configuration for your detected graphics card. The important thing is to add the option line for backingstore.

May 15th, 2011 by Moggen

I have installed Ubuntu 11.04 desktop as my new build environment for Emumiga (as a VirtualBox machine on my laptop). It comes with many packets for development installed already after base setup.

Here is a list of the extra packets I had to install to build AROS: automake, bison, flex, netpbm, libx11-dev and gcc-multilib. I also installed GIT as I’m using this for Emumiga development.

The reason for gcc-multilib is a bit tricky. I stumbled upon an Ubuntu bug (#778047). I got this error when building AROS: “include/linux/errno.h:4:23: error: asm/errno.h: No such file or directory”. Installing gcc-multilib fixes this.

May 11th, 2011 by Moggen

Yep, still alive.

Not much done lately. I’ve been occupied with other things, mainly my work.

I’m upgrading my build environment. I used a somewhat old Debian Lenny system as base for the development, but I want to set up a newer one. Running Debian Squeeze now, but I have some problems with it so I will probably install Ubuntu eventually. Upgraded to a more recent AROS codebase too, and I was positively surprised that it builds real cross compilers in the standard source package now. It used to be a contrib thing to get these. Thumbs up!

March 29th, 2011 by Moggen

Yup, got to square one (again).

Emumiga starts up again and runs the special exit instruction to quit.

I’m considering some kind of plugin system so support of libraries and devices can be added without requiring a recompile of all code. The question is, should I put them in their own libraries (load a library to emulate a library), or is it enough to LoadSeg() the plugins and just call the first address for it to set itself up? These things will not be shared so I guess a library is overkill.

February 27th, 2011 by Moggen

Yeah, I did. About time. It is about Emumiga in general and details of the new object model. It is to be included in the next source code bundle. But I’m so proud of it so I decided to upload it here right now. See it here: internals.txt.

The cpu emulation is converted to C++, and I’m working on the memory system. It is not too far left to the first checkpoint, that the emulator fires up, runs a couple of instructions, and then quit with a RTS instruction.