Cygwin setup: Difference between revisions
m (Added patch as autobuilder requirement) |
(→Setting up Cygwin: Some notes on building GCC4) |
||
| Line 4: | Line 4: | ||
Setting up Cygwin is fairly straight forward. Download and run the [http://www.cygwin.com/setup.exe installer] from the [http://www.cygwin.com/ Cygwin homepage]. Following the default setup will probably be OK, although it's advisable not to install it in a directory tree that uses a space (such as C:\Program Files\). Choose a suitable mirror 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.) |
Setting up Cygwin is fairly straight forward. Download and run the [http://www.cygwin.com/setup.exe installer] from the [http://www.cygwin.com/ Cygwin homepage]. Following the default setup will probably be OK, although it's advisable not to install it in a directory tree that uses a space (such as C:\Program Files\). Choose a suitable mirror 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.) |
||
'''For GCC 3.4.6:''' |
|||
* autoconf (version >=2.5) |
* autoconf (version >=2.5) |
||
* automake (version >=2.5) |
* automake (version >=2.5) |
||
| Line 15: | Line 17: | ||
* make |
* make |
||
* subversion |
* subversion |
||
| ⚫ | |||
'''For GCC4:''' |
|||
* autogen (This is currently (January 2008) not available via the cygwin installer) |
|||
* automake - must be version 1.9 (Be careful as the cygwin installer will try to install 1.10 every time you run it, as it is a dependency of libtool.) |
|||
* diffutils |
|||
* gcc |
|||
* libtool |
|||
* make |
|||
* makeinfo |
|||
* patch |
|||
* subversion |
|||
| ⚫ | |||
* cvs |
* cvs |
||
* glib |
* glib |
||
| Line 21: | Line 35: | ||
* patch |
* patch |
||
* pkg-config |
* pkg-config |
||
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 20:15, 29 January 2008
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, although it's advisable not to install it in a directory tree that uses a space (such as C:\Program Files\). Choose a suitable mirror 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.)
For GCC 3.4.6:
- autoconf (version >=2.5)
- automake (version >=2.5)
- binutils,
- bison
- flex
- gcc
- gcc-core
- gcc-g++
- gperf
- make
- subversion
For GCC4:
- autogen (This is currently (January 2008) not available via the cygwin installer)
- automake - must be version 1.9 (Be careful as the cygwin installer will try to install 1.10 every time you run it, as it is a dependency of libtool.)
- diffutils
- gcc
- libtool
- make
- makeinfo
- patch
- subversion
For the autobuilder:
- cvs
- glib
- libpopt0
- patch
- pkg-config
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:
Links
- Back to Using GCCSDK
| GCC and GCCSDK pages |
| GCC under RISC OS GCC for RISC OS, GCC tutorial, GCC common switches, GCC for beginners, UnixLib, ELFLoader |
