Cygwin setup

From RISC OS

(Difference between revisions)
Jump to: navigation, search
(Note on virus checkers)
(Add autobuilder requirements)
Line 15: Line 15:
* make
* make
* svn
* svn
 +
For the autobuilder
 +
* pkg-config
 +
* cvs
 +
* glib
 +
* libpopt0
If any of these are missing or you need to make changes, you can re-run the Cygwin setup program at any time.
If any of these are missing or you need to make changes, you can re-run the Cygwin setup program at any time.
Once this is done, running Cygwin from the Start menu or Desktop icon will present the "bash" console.
Once this is done, running Cygwin from the Start menu or Desktop icon will present the "bash" console.

Revision as of 19:59, 1 December 2006

Cygwin is a Linux-like environment for Windows. It can be used to cross-compile Linux applications for RISC OS.

Setting up Cygwin

Setting up Cygwin is fairly straight forward. Download and run the installer from the Cygwin homepage. Following the default setup will probably be OK. It's advisable not to install it in a directory tree that uses a space (such as C:\Program Files\). Choose a suitable mirror (e.g. ftp://mirror.ac.uk/) and make sure that the following (binary) packages are installed. (Most are found under the "devel" tree. Alternatively, choose "Full" view for an alphabetical list of all packages.)

  • autoconf (version >=2.5)
  • automake (version >=2.5)
  • binutils,
  • bison
  • flex
  • gcc
  • gcc-core
  • gcc-g++
  • gperf
  • make
  • svn

For the autobuilder

  • pkg-config
  • cvs
  • glib
  • libpopt0

If any of these are missing or you need to make changes, you can re-run the Cygwin setup program at any time. Once this is done, running Cygwin from the Start menu or Desktop icon will present the "bash" console.

If you have errors about the absence of autoconf/autoheader, but you have installed them, you may have to create links to the specific version you want to run:

$ ln -s /usr/bin/autoconf-2.5x /usr/bin/autoconf
$ ln -s /usr/bin/autoheader-2.5x /usr/bin/autoheader

It's also worth noting that virus checkers can slow down build processes considerably, since the build emits lots of temporary files and the virus checker insists on checking each one.

If you're not familiar with unix commands it might be worth doing a bit of research with Google. To get you started, you could try:

Links

Personal tools