So, i checked out AROS on my X86 machine a few minutes ago..

[Mazze]

cv643d wrote:
(If only AROS had integrated Amiga emulation for 68k programs)

*wishing*

This is the most wanted feature for AROS. Problem is that a Big-Endian emulator can't be easily implemented on a Little-Endian system.

What should be possible is a better integration of (E)UAE. This means networking, Picasso96 support etc.

[Mazze]

Steril707 wrote:

* Using CLI/Shell: i typed "endcli" to terminate the window, but instead the whole system started going down and booting up again. I wasn't sure if this behaviour is wanted or a known bug. It would also be nice to have "Ed" or any other editor starting up from within the shell, when being called.

This is an unknown and unwanted bug. At least I wasn't aware of it. BWT: You can report bugs at AROS' Bug Tracker.

AROS has a simple editor. Just type "editor" in a shell or start "system/tools/editor".

Can you give me an estimate how many people are working on the various parts of AROS?

There are about 5 people developing AROS core, most of them spare-time. And there are some people which write/port software for AROS.

[Mazze]

Steril707 wrote:
I guess there were some ideas about implementing a Java Virtual Machine for AROS before?

Anybody working on this already? Maybe a Kaffe port?

I found this projects on sourceforge:
jamiga
arosgjc

Both don't look very active

[Mazze]

Steril707 wrote:
But Jamiga was developed for OS4 and 3.9 ...

I guess AROS is not compatible to them, anyway, isn't it?

This depends on what functions of AOS3.9 it uses. The biggest difference between AOS3.1 and 3.9 is the ReAction GUI system.

[Mazze]

How do i integrate the Contrib. files into the aros folder i created? What do i do with all these nMake files?

Did you download the source code of contrib? You need the binary release "i386-all-contrib".

You'd need the metamake files if you want to build AROS by yourself from the sourcecode:
Compiling AROS Documentation

[Mazze]

Piru wrote:
@dammy

Painful upgrade, but it's now running FC7 x86_64 as AROS64's future build machine.

Excuse my ignorance, but why does AROS require you to run 64-bit OS to be able to build 64-bit version of it? Heck, you can even build things for different CPU, let alone 64bit target of the same CPU family...

There was recently a discussion about this on the Developer Mailing List. IIRC the reason was that the build system uses tools from the host system. A possible solution would be that AROS builds its own crosscompiler suite from the source.