OpenEmbedded Torrent

From Openmoko

(Difference between revisions)
Jump to: navigation, search
Line 3: Line 3:
 
The reason that these torrents are provided, is to decrease the amount of time it takes for system developers to have a fully functional build environment, allowing them to focus on more important tasks.  
 
The reason that these torrents are provided, is to decrease the amount of time it takes for system developers to have a fully functional build environment, allowing them to focus on more important tasks.  
  
{{Note|A pre-compiled OE environment is several gigabytes in size. For example, the compressed environment could be 3GB of data to download, but it might require another 16 GB to uncompress. It is suggested to have approximately 25GB of free disk space before continuing.}}
+
{{Note|A pre-compiled OE environment is several gigabytes in size. For example, the compressed environment could be 3GB of data to download, but it might require another 16 GB to uncompress. '''It is suggested to have approximately 25GB of free disk space before continuing'''.}}
  
 
Once the environment is downloaded via [http://en.wikipedia.org/wiki/BitTorrent BitTorrent], just follow these [http://wiki.openmoko.org/wiki/OpenEmbedded_Torrent_Instructions instructions], and go! See the list below for available torrents.  
 
Once the environment is downloaded via [http://en.wikipedia.org/wiki/BitTorrent BitTorrent], just follow these [http://wiki.openmoko.org/wiki/OpenEmbedded_Torrent_Instructions instructions], and go! See the list below for available torrents.  

Revision as of 22:07, 14 February 2009

The following links are in place to provide developers with a pre-compiled OpenEmbedded build environment tailored to their workstation's architecture. In order to use BitTorrent files, it is necessary to install a BitTorrent client.

The reason that these torrents are provided, is to decrease the amount of time it takes for system developers to have a fully functional build environment, allowing them to focus on more important tasks.

NOTE: A pre-compiled OE environment is several gigabytes in size. For example, the compressed environment could be 3GB of data to download, but it might require another 16 GB to uncompress. It is suggested to have approximately 25GB of free disk space before continuing.


Once the environment is downloaded via BitTorrent, just follow these instructions, and go! See the list below for available torrents.

Contents

Available Torrents

Linux Users

Torrents for Linux users

Mac OS X Users

Torrents for Mac OS X users

FreeBSD Users

Torrents for FreeBSD users

FAQ

  • Why does my environment rebuild gcc-cross, binutils-cross, libtool-native, ... ?

If every end-user had the same username and the same OE_HOME, then the cross-toolchain would be completely portable. However, that is generally not the case. The toolchain has compiled-in paths that contain system libraries and headers. If those paths change, then there is a very high probability that gremlins might attack you, your loved ones, and your town, possibly ruining Christmas for everyone.

Personal tools

The following links are in place to provide developers with a pre-compiled OpenEmbedded build environment tailored to their workstation's architecture. In order to use BitTorrent files, it is necessary to install a BitTorrent client.

The reason that these torrents are provided, is to decrease the amount of time it takes for system developers to have a fully functional build environment, allowing them to focus on more important tasks.

NOTE: A pre-compiled OE environment is several gigabytes in size. For example, the compressed environment could be 3GB of data to download, but it might require another 16 GB to uncompress. It is suggested to have approximately 25GB of free disk space before continuing.


Once the environment is downloaded via BitTorrent, just follow these instructions, and go! See the list below for available torrents.

Available Torrents

Linux Users

Torrents for Linux users

Mac OS X Users

Torrents for Mac OS X users

FreeBSD Users

Torrents for FreeBSD users

FAQ

  • Why does my environment rebuild gcc-cross, binutils-cross, libtool-native, ... ?

If every end-user had the same username and the same OE_HOME, then the cross-toolchain would be completely portable. However, that is generally not the case. The toolchain has compiled-in paths that contain system libraries and headers. If those paths change, then there is a very high probability that gremlins might attack you, your loved ones, and your town, possibly ruining Christmas for everyone.