**** BEGIN LOGGING AT Wed Oct 22 02:59:57 2008
Oct 22 12:57:14 <MacGyverNL> I have a question regarding the toolchain provided with optware for the OLEG wl500GP firmware. I've built the optware cross-compile environment according to the instructions on http://www.nslu2-linux.org/wiki/FAQ/Optware-uClibcBuild , section "And what if the program I need is not available in the existing packages?" I want to use this toolchain for a very simple package I'm creating myself. Now I'm in doubt on what to do: Copy the too
Oct 22 12:57:14 <MacGyverNL> lchain to a directory outside of optware and use it directly, or get it to work with a make/mypackage.mk file. Problem with the latter is that I don't understand what is needed for it to work. Does my package have to use the autoconf tools?
Oct 22 13:02:02 <kolla> well, what would MacGyver do? :)
Oct 22 13:02:36 <kolla> (no idea, just couldnt resist)
Oct 22 13:02:39 <MacGyverNL> MacGyver would probably have a better understanding about how this stuff works in the first place ;)
Oct 22 13:02:53 <MacGyverNL> In my case though I'm kind of making it up as I go along.
Oct 22 13:03:29 <MacGyverNL> I can compile by directly calling the compiler from the toolchain, already done some stuff by doing so.
Oct 22 13:03:42 <MacGyverNL> But that kind of defeats the point of having a build system in the first place.
Oct 22 13:04:10 <MacGyverNL> Otoh, I've never worked with the autoconf tools, wondering how hard it is to get right.
Oct 22 13:21:24 <MacGyverNL> Then again, I'm unsure if I even *need* the auto-tools. Optware wiki is a bit hazy on the subject of what is required of the packages you're trying to build.
Oct 22 13:36:22 <MacGyverNL> Okay, simplest of simple scenario's. I have a "package" that consists of a single source file. It doesn't need a configure script. All it needs is to use the correct compiler. What do I need to build an ipkg from that? I figure I need a Makefile containing the build instruction using the CC variable for compiler selection. Is this correct, and what else do I need?
Oct 22 20:15:47 <CIA-52> 03bzhou * r9197 10optware/trunk/make/py-beaker.mk: py-beaker: 1.0.2 -> 1.0.3
Oct 22 20:49:29 <rwhitby> MacGyverNL: you don't even need a Makefile if you don't want - you can put the C compiler commands directly in the optware makefile fragment.
Oct 22 20:50:17 <MacGyverNL> rwhitby: Thanks, but it's too late. I've succumbed to teaching myself autotools.
Oct 22 20:50:39 <rwhitby> But the usual case is that the software you are packaging has a Makefile or configure script already, and Optware just calls that in the appropriate way.  There is no one fixed interface to building each package, other than the optware makefile fragment <package>.mk which does the interfacing.
Oct 22 20:50:50 <rwhitby> MacGyverNL: autotools is as good as any other way.
**** ENDING LOGGING AT Thu Oct 23 02:59:57 2008