# HG changeset patch # User Paul Issott # Date 1336856626 -3600 # Node ID 95ba9a892bb403e519b02a1ae701a8898481509c # Parent 654e419824a9624ca2aacce5471942accb0a2baf Edit cross files diff -r 654e419824a9 -r 95ba9a892bb4 README --- a/README Sat May 12 22:04:31 2012 +0200 +++ b/README Sat May 12 22:03:46 2012 +0100 @@ -65,7 +65,7 @@ Cooker -------------------------------------------------------------------------------- The Cooker is a Build Bot which automates the build process but doesn't make -the dinner for you! We need quality receipts to cook succesfully and the goal +the dinner for you! We need quality receipts to cook successfully and the goal is not to have a bloated script so please Keep It Short and Simple. Cmdline tool : /usr/bin/cooker @@ -113,28 +113,28 @@ Cross ------------------------------------------------------------------------------- -See : doc/cross.txt -Istall: make install-cross -Usage : cross usage -Howto : cross howto +See : doc/cross.txt +Install: make install-cross +Usage : cross usage +Howto : cross howto Cross compiling -------------------------------------------------------------------------------- -Cookutils let you cross coile package fro a specofic architecture. Say you want -to build ARM binaries from an standard i486 machine. Cookutis provide helpers +Cookutils lets you cross compile a package for a specific architecture. Say you want +to build ARM binaries from a standard i486 machine. Cookutils provides helpers for the ARM platform, but the first thing to do is compile a cross toolchain and -modify the main cook.conf variables to use correct ARCH, CFLAGS and BUILD_SYSTEM +modify the main cook.conf variables to use a correct ARCH, CFLAGS and BUILD_SYSTEM -Cook handle HOST_ARCH and CROSS_* receipt variables. Some package dont build or -are not packaged for an architecture and so cross compiling will fails if the -package receipt have not been reviewd and include HOST_ARCH. Here is an example +Cook handles HOST_ARCH and CROSS_* receipt variables. Some packages don't build or +are not packaged for an architecture and so cross compiling will fail if the +package receipt has not been reviewed and includes HOST_ARCH. Here is an example and a list of cross variables: HOST_ARCH="i486 arm" CROSS_BUGS="Bugs description" -Before cross compiling, cook will automaticaly add cross-tools path to PATH, set +Before cross compiling, cook will automatically add cross-tools path to PATH, set CC, AR, LD, etc and also export CROSS_COMPILE. diff -r 654e419824a9 -r 95ba9a892bb4 cook.conf --- a/cook.conf Sat May 12 22:04:31 2012 +0200 +++ b/cook.conf Sat May 12 22:03:46 2012 +0100 @@ -51,7 +51,7 @@ # With -O2: binutils: Produce 14.0M Packed 5.5M Compressed 1.2M # With -Os: binutils: Produce 13.4M Packed 4.9M Compressed 1.1M # -# ARM: dont use -0s but -02 +# ARM: don't use -0s but -02 # ARM: -mcpu=name [arm9|xscale|...] or -march=name [armv4|armv6|...] # #MAKEFLAGS="-j$(($(grep processor /proc/cpuinfo | wc -l)+1))" @@ -59,7 +59,7 @@ CFLAGS="-march=$ARCH -Os -pipe -fomit-frame-pointer" CXXFLAGS="$CFLAGS" -# Binutils 2.22 break many packages build without LDFLAGS set correctly. +# Binutils 2.22 breaks many packages built without LDFLAGS set correctly. #LDFLAGS="-Wl,--copy-dt-needed-entries -lXt" # Default tool prefix for Binutils. diff -r 654e419824a9 -r 95ba9a892bb4 cross --- a/cross Sat May 12 22:04:31 2012 +0200 +++ b/cross Sat May 12 22:03:46 2012 +0100 @@ -21,7 +21,7 @@ Commands: howto Man alike and howto - info Dispaly cross-tools info + info Display cross-tools info testsuite Execute a small testsuite check-env Check build host tools download Download necessary sources @@ -113,7 +113,7 @@ make all-gcc all-target-libgcc || exit 1 make install-gcc install-target-libgcc cd $PREFIX/lib/gcc/$TARGET/$GCC_VERSION - echo "Creating symlink forstatic libgcc: libgcc_eh.a" + echo "Creating symlink for static libgcc: libgcc_eh.a" rm -f libgcc_eh.a && ln -s libgcc.a libgcc_eh.a } @@ -182,7 +182,7 @@ make install } -# Build Busybox to we can create prebuild tiny rootfs image and boot +# Build Busybox to we can create prebuilt tiny rootfs image and boot # from NFS ? cross_busybox() { echo "Extracting: busybox-$BUSYBOX_VERSION.tar.bz2" @@ -207,12 +207,12 @@ info) init_compile CC=${TARGET}-gcc - echo -e "\nCross Toolchain iformation" && separator + echo -e "\nCross Toolchain information" && separator [ "$config" ] && echo "Config file : $config" cat << EOT Target arch : $ARCH C Compiler : $CC -Additonal path : /usr/cross/$ARCH/bin +Additional path : /usr/cross/$ARCH/bin Build directory : $WORK EOT separator && echo "" @@ -246,7 +246,7 @@ download) download_src ;; clean) - echo -n "Remove all source files..." + echo -n "Removing all source files..." rm -rf $WORK/source/* && status [ "$log" ] && rm -f $WORK/log/*.log echo "To clean chroot: rm -rf $PREFIX" ;; diff -r 654e419824a9 -r 95ba9a892bb4 doc/cross.txt --- a/doc/cross.txt Sat May 12 22:04:31 2012 +0200 +++ b/doc/cross.txt Sat May 12 22:03:46 2012 +0100 @@ -4,7 +4,7 @@ DESCRIPTION Cross is a tool to build a cross toolchain on SliTaz GNU/Linux. The - ARM platform is actually supported and x86_64 toolchain is on the + ARM platform is actually supported and a x86_64 toolchain is on the stove COMMANDS @@ -17,10 +17,10 @@ HOWTO: When building a cross toolchain it's better to understand what is a - linker or or C compiler such as GCC. The configure option --target is - used by 'cross' to build cross-tools. When the toolchain is build on + linker or C compiler such as GCC. The configure option --target is + used by 'cross' to build cross-tools. When the toolchain is built on your machine you can then build packages with cook and the wok. Cross - use by default the same source tarball's than cook but path can by + uses by default the same source tarballs as cook but the path can be changed via the config file. Configuration is: cross.conf. Here is a cmdline howto: @@ -49,5 +49,5 @@ ------------------------ # cross testsuite -AUTHOR +AUTHORS Written by Christophe Lincoln