Hi Phil,

I think the ADK Package route is the way to go, but I'm not sure, 
looking at it where to start.

I looked in the docs dir at the single-package template, but it doesn't 
really explain what it's doing!

Would you be prepared to talk me through building a simple hello world 
package?

If you could do that, I'd be happy to write it up as a tutorial 
afterwards :)

Alan


Phil Sutter wrote:
> Hey Alan,
> 
> I'm fullquoting here, cause I'd like to have the full conversation held
> in freewrt-users@ as this might interest others as well.
> 
> On Mon, Jul 13, 2009 at 10:59:30AM +0100, alan lenton wrote:
>> Hi Phil,
>>
>> My apologies for being obscure :)
>>
>> I have an application, written in C++, that uses libcurl to run tests on 
>> what the real speed of the line is. I originally developed this for an Alix 
>> box which was running the current version of OpenWrt. I now need to port it 
>> to a LinkSys wrt54gl, which is running FreeWrt.
>>
>> With the Alix there was a separate SDK which took my source code and its 
>> makefile, built a binary suitable for OpenWrt on the Alix and also provided 
>> a .ipk package.
>>
>> I was wondering it there was a similar tool for FreeWrt, and if not, how I 
>> would go about building a non-standard binary from scratch.
>>
>> I'm sorry if the answer is obvious, but I'm pretty new to embedded 
>> programming, even though I've been programming Linux since 1992 (basically 
>> server stuff).
>>
>> Thanks for replying,
>>
>> Alan
> 
> Well, there is nothing supporting out-of-tree builds in the FreeWRT ADK,
> but I'd recommend integrating your code into the ADK instead. So you may
> want to have a look at other packages in the package/ subdirectory.
> Although it looks complicated in the beginning, it's actually quite
> straight forward to port new packages, even for new users. If you have
> any questions, don't hesitate generating some traffic on this list. :)
> 
> OTOH you could try an out-of-tree build. The cross tools are in
> cross_mipsel/host/bin (for mipsel targets, of course), headers and
> libraries are in cross_mipsel/target/{lib,include}. Also for each
> library in packages/, if you have enabled it in menuconfig, it will be
> put into cross_mipsel/target. So if you need curl, just activate
> libcurl, run a build and your cross tools should be complete. :)
> 
> Good luck, Phil
> 
_______________________________________________
freewrt-users mailing list
freewrt-users@freewrt.org
https://www.freewrt.org/lists/listinfo/freewrt-users

Reply via email to