y. Please take a look at my (simple) Makefile
> attached. I am trying to figure out how to organize my files into the
> following structure:
>
> inc/
> src/
> build/
> build/armv4t/ (which will contain an 'obj' folder and the final binary)
> build/x86/ ( - do - )
>
I had a follow-up query. Please take a look at my (simple) Makefile
attached. I am trying to figure out how to organize my files into the
following structure:
inc/
src/
build/
build/armv4t/ (which will contain an 'obj' folder and the final binary)
build/x86/ ( - do - )
How do I alte
ry comfortable with the 'autoconf' way
> > of doing things. I usually prefer a simple Makefile / Scons file.
> No problem, just replace all occurances of gcc with
> arm-angstrom-gneabi-gcc (same for g++, ld, strip, ...).
>
> Personally I use a combination of autoconf and
Hello
> I set up the toolchain as per the instructions on the wiki and was
> able to build and package the sample project as per the tutorial.
>
> My problem is that I am not very comfortable with the 'autoconf' way
> of doing things. I usually prefer a simple Makefile
lem is that I am not very comfortable with the 'autoconf' way of
>> doing things. I usually prefer a simple Makefile / Scons file.
I'm afraid my answer would be that autoconf has an incredibly steep
learning curve, but it really is the right way to do it.
_
'autoconf' way of
> doing things. I usually prefer a simple Makefile / Scons file.
>
> I am assuming I can make do with a simple Makefile right? It's not like the
> target hardware/platform is changing a lot for an Openmoko project. Possibly
> I can have different targets fo
I set up the toolchain as per the instructions on the wiki and was able to
build and package the sample project as per the tutorial.
My problem is that I am not very comfortable with the 'autoconf' way of
doing things. I usually prefer a simple Makefile / Scons file.
I am assuming I c
