well I just have to wait for me to get a computer that I bought from a friend and then I do some tests, but I have to install the sdk also

in most cases, if you have sources checked out with svn, which are still pretty up to date, you only need "svn up" to resync with the late changes in the main repository.

then you only need to do "make" in your build directory.

the build system will usually recognize, what has changed since the last time and only rebuild the necessary modules.

this spares a lot of time.

also. if you just want to build a single module (program, library or directory) you simply append the name of that module behind make. the names of the modules are to be found in the respecitve meta makefiles (mmakefile.src) in the source.

for instance just to build frying pan you type:

"make contrib-fryingpan"

sometimes you can add "-quick" to module name to build just the module without re-checking and eventually rebuilding the dependencies.

you may also append "-clean" to module name to remove the previously built files, just to be sure.

ok thank you

Quote:

imho, the easiest thing is just to compile everything, along with the toolchain, just issuing "make". few years old source and certainly binaries will be severely outdated, so that they will cause unexpected problems, where they may not exist anymore.

to effectively contribute imho, its important to work on as up to date material, as possible.

I used ubuntu 12.04 when I was convinced and it was fine, now I downloaded the last lts

I had managed to compile it a few years ago from the sources of aros, but for the software is the same thing ?, I have to compile everything in the source tree?

thank you wawa

Quote:

so, you actually have ubuntu set up?

****************************************

from there it should be straight forward:
http://aros.sourceforge.net/documentation/developers/compiling.php


all i can do is to requote it:

"sudo apt-get install" packages listed under requirements. you can use that synaptic package tool as well. sometimes you may have to figure out the proper package name, but its mostly just the one listed. linux user shouldnt have problem here.

if you forget something aros build will break later and tell you about some missing header. no problem then. you simply check, which package contains this header, install it, hit make again and watch aros progress with build.

****************************************

now, down the page is "get the sources" section.

you can checkout the sources somewhere to your "home" directory:
Quote:

myself, ive crated AROS-source dir there. so, most convenient is building aros in another own directory, outside aros source dir, preferably at the same level, to keep things clean.

for instance i created a number of directories for target architectures, such as "aros-x86-630", to reflect the target and the compiler used. but you can call it as you want, for instance simply "aros-build" or so.

now in your shell, you cd to your build directory and configure.

my usual configure line for x86 looks like that:
Quote:

but actually you only need something like:
Quote:

portsources flag is used in order to cache source tarballs of outside components somewhere on your drive, not to download them again and again, in my case:
Quote:

the following is optional, and specifies a newer toolchain version. without it you will compile with gcc-4.6.4. usually you can ommit it and be fine with that, however keep in mind, you need it to build odyssey later.
Quote:

in conclusion i advise to actually use all the above configure flags, inclusive debug, for serial debugging.

I found this, if you can compile with netbeans well

http://amifreak.ftp.sh/post/setting-up-environment-to-start

hi

I wanted to understand how to build my cross environment under ubuntu, to help if it is possible to bring something on abiv1, after I install linux and builds-essentials what should I do?

thank you