Hi all. I have done support for multiple subarchs (or even different configs for one subarch), and it seems that it will work OK. Currently new subarch requires: 1) record in KARCHS variable in MasterInclude.mk with it's name 2) patch file into linux package, with name $(CONFIGNAME.config)-$(SUBARCH).patch 3) separate package description in initrd buildtool.cfg 4) separate package description in kmodules buildtool.cfg
I also removed symlink linux in the linux package directory - it is meanless now. About kernel-dependent package building: 1) some packages requires path to kernel include directory - just replace in path $(BT_LINUX_DIR) to $(BT_LINUX_DIR)-$(BT_KERNEL_VERSION) 2) some packages (like accel-pptp's patched poptop) requires path to include/linux/version.h - so they wants path to linux-$(SUBARCH); IMHO it'll be enough to specify path to any building dir. 3) kernel modules (drivers & etc) - they must be rebuilded for _each_ subarch & module must be copied to corresponding directory (for examples - look at accel-pptp) ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
