This directory contains the build system for Fatdog64.

It is similar to the build system used to build Fatdog itself,
except that it works directly on the running FatdogArm and there is 
no need to set-up a separate chroot directory.

It takes the same 'recipe' format; a properly prepared 'recipe' file will 
compile and build on both the chroot-build system and this build-system,
producing identical output. 

Of course, you don't have to use this, as Fatdog64 package management
uses Slackware's, you can just use regular Slackbuilds. But using
this system gives you the benefit of being able to integrate the package
for upstream builds (in the chroot build system).

build-pkg.sh    will build a single package. All packages are specified
                in 'pkg' directory under this directory.
                (The 'source' directory contains packages of already 
                installed applications, useful for you to use as 
                starter template for customising your own packages).
all-rebuild.sh  will build packages specified in build-pkglist.
                it will automatically rebuild a package if the recipe
                is newer than the built/installed one.
functions.sh    contains helper functions used by build-pkg.sh
env.sh          contains common variables used by packages, usually
                set to specify CFLAGS, LDFLAGS, parallel make builds, 
                etc.
                env.sh automatically configures many variables for
                32-bit or 64-bit, depending on PKGARCH you specify in
                your recipe.
build-pkglist   is a sample file.
pkg/shell       is a sample recipe directory, commented as necessary.
migrate-pkg.sh  is a script to migrate from Fatdog64 700 `recipe file`
                into this versions's `recipe directory`.

This directory is self contained; you can copy this entire directory 
elsewhere and make your build on the the new location.

Note that by default the temporary BUILD_DIR is located in /tmp; if you're
running low on memory and/or building huge packages like Samba or Seamonkey
browser, you may want to point it elsewhere *outside* your root filesystem
(e.g in /mnt/sda5 or whatever). 

James Budiono, 2016.
