<div dir="ltr">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:<br><br>inc/<br>src/<br>build/<br>build/armv4t/ (which will contain an 'obj' folder and the final binary)<br>
build/x86/ ( - do - )<br><br>How do I alter the '%.o: %.c' directive so that it picks up the .c from src/ and drops the .o into build/<arch>/obj/ , and link the objs into the final executable at build/<arch>/ ? <br>
<br><div class="gmail_quote">On Tue, Aug 5, 2008 at 8:41 AM, sparky mat <span dir="ltr"><<a href="mailto:max@sparkymat.net">max@sparkymat.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div dir="ltr"><div class="Ih2E3d">On Mon, Aug 4, 2008 at 1:14 PM, Roland Schatz <span dir="ltr"><<a href="mailto:roland.schatz@students.jku.at" target="_blank">roland.schatz@students.jku.at</a>></span> wrote:<br></div>
<div><div></div><div class="Wj3C7c"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello<br>
<div>> I set up the toolchain as per the instructions on the wiki and was<br>
> able to build and package the sample project as per the tutorial.<br>
><br>
> My problem is that I am not very comfortable with the 'autoconf' way<br>
> of doing things. I usually prefer a simple Makefile / Scons file.<br>
</div>No problem, just replace all occurances of gcc with<br>
arm-angstrom-gneabi-gcc (same for g++, ld, strip, ...).<br>
<br>
Personally I use a combination of autoconf and hand-written makefiles<br>
(no automake), but I see no problem doing the same thing without autoconf.<br>
What I do is just setting a HOST variable in the makefile, and then<br>
compile using $(HOST)-gcc, and putting all target files into the<br>
bin.$(HOST) directory.<br>
<div>> I am assuming I can make do with a simple Makefile right? It's not<br>
> like the target hardware/platform is changing a lot for an Openmoko<br>
> project. Possibly I can have different targets for ARMv4T build and<br>
> x86 build. So I needed some help with this:<br>
><br>
> I could see the usually libraries - libc, libdl, libcrypt, libgcc,<br>
> libpthread .. etc. in<br>
> /usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/lib . What about<br>
> the windowing toolkit libraries - GTK+, Qt - libraries? What about X<br>
> libraries? How do I get more libraries (that have been ported)?<br>
</div>Most libraries are in<br>
/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr/lib. If some are<br>
missing, you can just install them on the host using "./configure<br>
--prefix=/usr/local/openmoko/arm/arm-angstrom-linux-gnueabi/usr<br>
--host=arm-angstrom-linux-gnueabi; make; make install".<br>
<div><div></div><div><br>
</div></div></blockquote></div><br></div></div>Yay!! 'Hello World' working on my phone!! Yipeeee... feel so awesome!!<br></div>
</blockquote></div><br></div>