Difference between revisions of "WindowsInstall"
(→Prerequisites for Window$ installation: put packages in alphabetical order) |
|||
Line 9: | Line 9: | ||
Choose the default installation (nothing to modify) and add the following packages by clicking one time on the "skip" icon: | Choose the default installation (nothing to modify) and add the following packages by clicking one time on the "skip" icon: | ||
− | * devel -> | + | * devel -> binutils |
− | * devel -> | + | * devel -> bison |
− | * devel -> | + | * devel -> flex |
* devel -> gcc-core | * devel -> gcc-core | ||
* devel -> gcc-g++ | * devel -> gcc-g++ | ||
* devel -> gdb | * devel -> gdb | ||
− | |||
− | |||
* devel -> gettext-devel | * devel -> gettext-devel | ||
− | * devel -> | + | * devel -> libncurses-devel |
− | * devel -> | + | * devel -> make |
+ | * devel -> patchutils | ||
+ | * devel -> subversion | ||
* system -> util-linux | * system -> util-linux | ||
* web -> wget | * web -> wget |
Revision as of 20:46, 18 October 2006
How-To install Armadeus Software Development Kit for Window$
The toolchain can also be built on a windows system. To do this, Cygwin (a Linux emulation tool) has to be installed first.
Contents
Prerequisites for Window$ installation
Install cygwin: http://www.cygwin.com Remark: do not delete the package folder (ftp%xxxx) otherwise the synchronization between the installed packages and the available ones will no more be done !
Choose the default installation (nothing to modify) and add the following packages by clicking one time on the "skip" icon:
- devel -> binutils
- devel -> bison
- devel -> flex
- devel -> gcc-core
- devel -> gcc-g++
- devel -> gdb
- devel -> gettext-devel
- devel -> libncurses-devel
- devel -> make
- devel -> patchutils
- devel -> subversion
- system -> util-linux
- web -> wget
Installation
Open a cygwin shell and follow this procedure:
Get Armadeus software
$ svn co svn://ericjarrige.homelinux.org/armadeus/trunk armadeus --username <<YOUR USERNAME>> --password <<YOUR PASS>>
A directory named armadeus/ will be created on your hard-disk and will contain all the files you need.
If not, then download installation archive from SourceForge: http://sourceforge.net/projects/armadeus and detar it (tar -xvf filename).
Configure Armadeus software
$ cd armadeus/ $ make menuconfig (or just make the first time).
This will launch the buildroot configuration. in Board Support Option menu, select your armadeus board (apf/apm9328), the RAM size (16/32MB) and so on...
- Choose GDB version 6.3 if you need a debugger
- If you need the LIBSTD C++, add this in the menuconfig/toolchain options/additional gcc options:
--disable-libstdcxx-pch. This will disable the use of the precompiler headers
- Exit the configuration tool and save your config
Launch build
$ make
The toolchain is built automatically. During this procedure, several files are downloaded from the web. Please wait for a while.... it takes at least one hour for the first run!
Known Problems
- compilation crash with uclibc-0.9.28: run make again
- compilation crash with gdb 6.3: run make again
- compilation crash with linux 2.6.12: run make again
Enjoy the result
The generated binary files can be found in the subdirectory armadeus/software/buildroot:
- u-boot.brec (can be used with the bootstrap, if U-Boot is not installed or not working, see BootLoader page)
- u-boot.bin (for download with uboot, see BootLoader "Update u-boot" page)
- linux-kernel-2.6.xx-arm.bin (for download with uboot, see InstallLinux)
- rootfs.arm_nfpu.jffs2 (for download with uboot, see InstallFileSystem?)
- rootfs.arm_nfpu.tar (for an nfsroot, see RootNFS?)
To keep your copy up-to-date within the armadeus tree
$ svn update
This will update your working directory to the latest release.
Note: if "svn update" fails because a directory or a file already exists, then do:
$ rm -rf <this-directory/file> $ svn update
You can do a:
$ make defconfig
to have the latest features automatically activated and a
$ make menuconfig
to set again your personnal parameters (SDRAM size...).
You have to do a make to rebuild binary files end then upload the binary files to your target.
Note: if definitively everything goes wrong while it worked before the last update. You can apply the following procedure:
$ rm -rf software/buildroot $ rm Makefile $ make $ make