Le 27/03/2012 22:04, davidMbrooke a écrit : > Thanks Mike. I have now completed the document based on what was in my > head. It now describes all the places where the build system has to be > configured in order to add a custom toolchain (really only 3 places - > some simple config settings in make/MasterInclude.mk, a custom patch for > the Linux kernel .config and a custom uClibc .config). > > I have also started a Discussion page at the same location to track Q&A. > > david > Thanks david for the documentation. Just some questions: i have a soekris net6501 board (with an Atom E6xx series processor). If i take the "standard" configuration (|i486-unknown-linux-uclibc) buildtoo.pl will use the parameters defined in ||make/MasterInclude.mk: |
ARCH:=i386 KARCHS:=i686 i486 geode KARCHS_PCIE:=i686 ARCH_CFLAGS=-march=i486 -mtune=pentiumpro I think it's not optimal for my board (i don't have to compile for i486 and mtune can be more specific). So my question: what is the best changes i need to do to have optimisation for my board ? I think i need a specific triplet name like atom-net6501-linux-uclibc ? with in|make/MasterInclude.mk:| |else ifeq ($(GNU_TARGET_NAME),atom-net6501-linux-uclibc) # Primary kernel architecture export ARCH:=x86_64 # Space-separated list of kernel sub-archs to generate export KARCHS:=net6501| export KARCHS_PCIE:=net6501 |# Arch-specific CFLAGS export ARCH_CFLAGS=-march=atom -mtune=atom is it right (like the |KARCHS_PCIE) |? This is just a use case to understand how we can change things for a proper toolchain. Regards, Yves || | ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
