* create a toolchain for the new platform
* create a platforms/toolchain-
.mk GNU_TARGET_NAME will be used in almost all package configuration it usually should match the output of `make query-TARGET_CC` -dumpmachine * [optional but recommended] automate toolchain creation * create a platforms/packages-
.mk * make
-target cd
make directories ipkg-utils make toolchain * make hello-ipk * add an entry to %target_to_bintype in scripts/optware-check-package.pl with `file binary` regex pattern, after that you can run make hello-check * set NO_BUILTIN_MATH correctly in platforms/toolchain-
.mk set GETTEXT_NLS correctly in platforms/toolchain-
.mk * provide LIBNSL_VERSION in platforms/toolchain-
.mk * if libstdc++, fill-in libstdc++ version in platforms/toolchain-
.mk if exclusively libuclibc++, work out the libstdc++ wrapper * to test the build of a C++ program, you can try make re2c-check `make query-TARGET_CROSS`objdump -p builds/re2c-*-ipk/opt/bin/re2c | grep NEED * it's a good idea to get perl working early by providing a config.sh under sources/perl/Cross/ either a config.sh-
or config.sh-$(GNU_TARGET_NAME) the following packages conditionally depends on the presence of perl: grep -l ifeq.*filter.*perl make/*.mk so enable the feed after getting perl working, or rebuild these packages. * if there is no firmware support for ipkg, or if you want to keep ipk installation entirely independent under /opt, you may want to build and include ipkg-opt in SPECIFIC_PACKAGES of platforms/packages-
.mk see http://www.nslu2-linux.org/wiki/Optware/Slugosbe for an example of manual bootstrap.