Quote:

Murks!IDE 0.6.0 is already there, so gcc and g++ should be there. Configure is'n available and make is already installed. Maybe I'm not so far from the goal.

Quote:

If you have problems setting up GCC package (gcc & g++), please drop me an email and I will help you. As for the other tools to make a full chain (configure & make) I don't think they are available yet for AROS.

Quote:

Those assigns have already been included in VmwAROS user-startup. What I'm not aware of, unluckily, are the packets I should install (and where to do it) to make VmwAROS usable for development jobs.

Nevermind, I just found that I mxed up directories. I just compiled my first program on Aros, this is so cool!
:cheers:

I've got to dig this one out again...

Quote:

Should these assigns be sufficient for gcc to know where to search the includes? It doesn't find stdio.h and the like when I try to compile something. Sorry for the noob mode, but you've got to start somewhere...

Thanks. I've given up on trying to compile within AROS at the moment.

I just downloaded a VMWare image of Ubuntu Desktop 8.04, and plan to compile from within that. At least I know the Linux tools exist and work (at least I assume they will).

It seems that this is necessary until someone creates a AROS bash shell or something similar, for the single purpose of getting the linux specific AROS build scripts run. (I realise some other things must be needed too, else Cygwin would compile AROS)
Makes me wonder if people really want to have a non-Linux compile environment at all ?

Everyone - keep up the good work. Hopefully one day I will actually contribute something more useful than comments.

Cheers

AROS isnt compiled from the subdirectories but always from the top level of the source tree.

This is primarily because it allows us to be certain where to find files needed to set particular build-time options, and so that things such as metamake know exactly where to start looking for "makefiles" that describe the components that other parts may require before they can be compiled/linked/used.

To compile only a particular item requires using the ****-quick targets (ie type make bootiso-quick etc - in this case it would only perform the step of trying to create the actual iso binary but will likely fail if you havent already compiled the other components of AROS, and is only listed here as an example of a -quick target).

Some things ofcourse need to be done differently - such as compiling the AHI drivers. Thats because they dont directly use the AROS build system but use their own configure/Makefiles that the AROS build system just invokes.

Yes, the biggest problem for someone new to it is probably the lack of documentation, but then again most people learn best not from reading but from trying/doing ;)

Its not that hard to follow tbh, so long as your willing to try and understand it.

I'm certainly not the right person to speak, but I think this problem is related to the fact that AROS isn't able to self-compile yet. So AFAIK our gcc is able so far to compile standalone programs, but not AROS elements themselves (nor anything which relies on the development toolchain on Linux), which need MetaMake and several other tools... Hence the bounty.

Paolo, I think the assigns for it will be located in the INSTALL text file in the System:Development drawer.

I've more-than-once asked for help, here and everywhere, in order to be instructed how to place GCC files and assigns correctly, but none answered. Creating a working development chain inside of VmwAROS is absolutely in the schedule, however I don't know exactly when it will be done. In the meanwhile, you can look for WinAROS and DevAROS which both have it.