On Fri, 2010-02-19 at 16:14 +0100, Felix Fietkau wrote: > On 2010-02-19 2:53 PM, David Farrell wrote: (..) > > I just want to treat the OpenWrt system as a general purpose embedded linux > > box. > Two possibilities: > > a) You read about how the Linux kernel is cross compiled, how to build > external kernel module trees and so on using variables like > CROSS_COMPILE, ARCH, M, ... > The kernel sources are in build_dir/linux-*/linux-*/. > You can put the toolchain dir into your PATH and call the make commands > there (pointing at your external tree), either manually or with your > wrapper makefile. >
How about the OpenWRT SDK? Is that still supported? I never used it, but it would be useful if it would contain some Makefiles and/or scripts to help building user space and kernel space code outside the OpenWRT tree. The idea is that you install a pre-compiled SDK somewhere, source a script with settings and you can easily build your own stuff without hassle about paths and stuff. This is how most board support packages from hardware manufacturers work. It should be as easy as native compilation. b) You realize that cross-compiling an external kernel module is much > easier with OpenWrt, and simply copy a package dir like > package/spi-ks8995 and adjust it for your own kernel module, then run > make oldconfig and then run make package/<yourpackage>/compile V=99 ;) > Yes, it is easy to create an external package and include it in the OpenWRT build. Is there a way to build an OpenWRT image with calling "make" outside the OpenWRT tree and have the image also outside the OpenWRT tree? The idea here is to keep your code and OpenWRT separated during development. Bas. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
