compiling instructions for aros68k

[wawa]

by request from here:
http://eab.abime.net/showthread.php?t=84430&page=18
i am opening a separate thread for those interested about how to get aros compile and run either under uae or on an amiga.

if you want to check it out via svn, there is full instructions to do so on aros portal. namely here:
http://aros.sourceforge.net/document.../compiling.php
scroll down the page:

> svn checkout https://svn.aros.org/svn/aros/trunk/AROS
> cd AROS
> svn checkout https://svn.aros.org/svn/aros/trunk/contrib

given you have all necessary packages installed you can then make a build dir and from there invoke configure, with some - your preffered - options, like:
--target=amiga-m68k
--with-serial-debug (if you want serial debug)
--enable-debug (if you want debug symbols compiled in)
--with-portssources=.. (if you want contributed archives and toolchain sources stored locally instead downloading them anew)
--with-gcc-version=6.3.0 --with-binutils-version=2.25 (if you want the neweat toolchain)

and then simply..

make (-s)

i can tell you how to compile a part of the source (a module) but if you want to use another (external) compiler, you will have to experiment on yourself.

[ross]

Thanks wawa!

Some addendum:
if you prefer GIT there is Jason repository mirror at:
https://github.com/ezrec/AROS-mirror
then you can clone in ./AROS

If you prefer to make separate cross compiler toolchain (like me), in your work dir (that can be even ~) you need to:
- mkdir AROS-build (where aros-m68k will be build)
- mkdir m68k-aros-build (where cross compiler toolchain will be built)
- cd m68k-aros-build
- ../AROS/configure --target=amiga-m68k --with-aros-toolchain-install=/opt/m68k-aros [plus all the wawa explained options]
- make -s crosstools
- cd ../AROS-build/
- ../AROS/configure --target=amiga-m68k --with-aros-toolchain-install=/opt/m68k-aros --with-aros-toolchain=yes [--enable-debug --with-serial-debug=yes]
- make [-s]

(in /opt/m68k-aros lies the toolchain)
(in ~/AROS-build all the goodies)

Cheers,
ross

[Locutus]

That really does look pretty painless, including build scripts for the required cross compiler toolchain is a very nice touch.

I'll give it a go once i have some free time.

[wawa]

Originally Posted by ross

If you prefer to make separate cross compiler toolchain (like me), in your work dir...

thats a similar method as the one i used initially. with the exception that i have been installing the toolchain in opt as described here:
http://www.amigaforum.de/index.php?t....msg200#msg200
i have not done separate toolchain build since a while and im not sure if i would advise it. best is to keep up to the whole amount of changes at once and the toolchain elements or sdk also get updated constantly, not only the aros code as such.

my practice is to check out aros into the homedir like that: /AROS-source/AROS/contribs

and then create directories for parallel builds on the same level, labelled like aros-m68k-630 or aros-x86-464 in order to test and work on different platforms and compilers in parallel from the same source. you simply need to keep in mind to reconfigure. other than that i put a local potrssources dir on the same level to conserve time and bandwidth.

[wawa]

Originally Posted by Locutus

That really does look pretty painless

it is painless, for the most part. you can even compile module for module, library for library or directory for directory. all you need to, is to go and look at local mmakefile.src in the sources you are interetsed in and identify
a module name. for instance, to compile png.library you go to

/AROS-source/AROS/workbench/libs/png

check mmakefile.src, see right away this line:

#MM workbench-libs-png : workbench-libs-z

then you simply do

make workbench-libs-png

and the library gets built along with all dependencies.

if you have dependencies built already you can

make workbench-libs-png-quick

..usually.

if you now want all libraries to be built or rebuilt, assuming you might have done some changes you want to test, you simply go level up:

make workbench-libs

[ross]

Originally Posted by wawa

you can even compile module for module, library for library or directory for directory

You spared me to ask

Thanks very much,
ross

[Locutus]

Small catch, the SVN repo doesn't have Anonymous read only access... (wth..)

At the request of Amiga Inc., anonymous read-only access to the repository has been disabled.

I'll grab the git mirror :-)

[wawa]

are you sure? ;O

where have you seen it? i doubt amigainc is being currently in position of requesting anything like that. it must be an old notice, i believe to remember when anon access has been enabled.

[ross]

http://www.amiga.org/forums/showpost...5&postcount=19
(05-30-2007, 03:44 AM)

[wawa]

[ross]

cygwin compilation --with-gcc-version=6.3.0 --with-binutils-version=2.25

no errors

[wawa]

you might check out contribs and ports

[wawa]

in case anyone tries to boot aros on an amiga to date there has been some issues lately. toni has commited some fixes but one yet remains to be researched.
also kalamatee added some checks for proper rom sizes and some changes that look like will enable us to properly use gdb with the debug builds.

so stand by.

[ross]

Originally Posted by wawa

in case anyone tries to boot aros on an amiga to date there has been some issues lately. toni has commited some fixes but one yet remains to be researched.
also kalamatee added some checks for proper rom sizes and some changes that look like will enable us to properly use gdb with the debug builds.

so stand by.

No boot problems here.. compiled from 10/05 commit (before 11-12/05 twilen/nicja patch)

I had noticed that the main ROM was almost full (up to $fffd00).
Maybe code fit thanks to GCC6.3.0 compile?

[EDIT: sorry, read in a hurry.. WinUAE used]
[EDIT2: tested with a Blizzard -> no boot]

ross

[wawa]

aros boots on my a1200 with blizzard1260/16mb.
however there is still crash while AddUSBClasses.
one could comment it out in the s-s, i dont have any usb hardware there, let alone if the stack was even woking for now.
but im giving it a shot to debug, since toni beats me to it.

edit: looks like i found it.

[ross]

Originally Posted by wawa

aros boots on my a1200 with blizzard1260/16mb.

Good, with last commits boot also on Blizzard 1230IV

ross

[wawa]

Originally Posted by ross

Good, with last commits boot also on Blizzard 1230IV

ross

has it ben fixed? i cant determine just by looking at the commits. according to toni it is a compiler bug. that explains why the nightly doesnt exhibit wrong behaviour. it is still being compiled with 4.6.4.

[ross]

Originally Posted by wawa

has it ben fixed? i cant determine just by looking at the commits. according to toni it is a compiler bug. that explains why the nightly doesnt exhibit wrong behaviour. it is still being compiled with 4.6.4.

I've only recompiled the nightly build (not the toolchain, so assume the preceding 6.3.0 gcc and all).
Can be previously my bad, but today AROS and Blizzard agree

Bye,
ross

[Toni Wilen]

AddUSBClasses crash is compiler bug, Blizzard arosbootstrap crash was rom image memory allocation problem (54665/54666), which worked accidentally with older compiler.