>> 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? .Why do you want to call it outside of the tree? You can keep your >packages as a separate feed, which makes it easy to keep track of your >own work without having to fully integrate it into the OpenWrt tree. >- Felix I created a package in the tree called template. The kernel module builds and loads fine. In the course of putting it in a package I have to choose CONFIG_MOD_TEMPLATE and a couple other items in a manner which doesn't conflict with existing options. I don't really need to be part of menuconf, I don't need these options. I also tried the V=99 option, to see what is happening. The output from this is a little too verbose for me. My plan now is to try to find out how obj-m is processed on my ubuntu install to see how I can apply this to the openwrt toolchain. David. _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
