If you would prefer to use pre-built images, those are also available. Gumstix maintains an autobuild system that checks out and does a clean build of the source tree twice daily. Binaries are available for connex and verdex in both glibc and uclibc versions (basix users should select the connex version). Binaries for u-boot are also available.

 

 

Where to find them

The base url for all of the binaries is:

http://www.gumstix.net/feeds

You will find three subdirectories at this location: u-boot, archive, current.

u-boot

The u-boot subdirectory contains prebuilt binaries for each of the gumstix product lines. The filenames are of the form:

u-boot-{family}-{clock speed}-{revision}.bin

So, for example, the file named u-boot-connex-200-r1578.bin is intended for a 200Mhz connex motherboard and the binary was built from revision 1578. Basix users should use a connex image which matches their motherboard clock rate.

archive

As its name implies, the archive subdirectory contains an archive of previous builds. The subdirectories of archive are named for the revision number of the source code used for the build.

Beneath each archive revision subdirectory is the following substructure:

glibc
|-images
| |-gumstix-custom-connex
| `-gumstix-custom-verdex
`-ipk
uclibc
|-images
| |-gumstix-custom-connex
| `-gumstix-custom-verdex
`-ipk

This structure should be fairly self explanatory: glibc images are contained in the glibc/images directory and uclibc images in the uclibc/images directory. Connex images will be in the gumstix-custom-connex subdirectory and verdex images in gumstix-custom-verdex. As always, basix users should select images from the connex directory.

The ipk directories contain a large number of ipkg files. In general, you won't need to look there unless you need a software package built from a particular source code revision or you want to download and install an ipkg file by hand.

Normally you will install packages using the ipkg tool on your gumstix. The tool will automatically look in feeds/current as its source for software packages.

current

As mentioned above, this directory is where the ipkg package management tool acquires its packages. Its directory structure is identical to the individual build subdirectories described above in archive.

In fact the contents of this directory are just a copy of the most recent "good" build in the archive.