Cygwin setup


(Difference between revisions)
Jump to: navigation, search
m (Fixed vandalism. What is it with these idiots?)
Line 11: Line 11:
* gcc
* gcc
* gcc-core
* gcc-core
* gcc-g
* gcc-g++
* gperf
* gperf
* make
* make

Revision as of 12:01, 10 June 2007

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. 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.

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:


GCC and GCCSDK pages

GCC for RISC OS, GCC tutorial, GCC common switches, GCC for beginners, UnixLib, ELFLoader
GCCSDK and Unix porting
GCCSDK, GCCSDK Releases, GCCSDK Development, Using GCCSDK, Autobuilder Development and Packaging Cygwin setup, Accelerating autobuilder with apt-proxy, ChoX11, Developer help wanted

Personal tools