OpenEmbedded Torrent

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(catchg)
 
(4 intermediate revisions by one user not shown)
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.  
Line 12: Line 12:
  
 
Torrents for Linux users
 
Torrents for Linux users
 +
 +
(There are no torrents at this time)
  
 
=== Mac OS X Users ===
 
=== Mac OS X Users ===
  
 
Torrents for Mac OS X users
 
Torrents for Mac OS X users
 +
 +
(There are no torrents at this time)
  
 
=== FreeBSD Users ===
 
=== FreeBSD Users ===
  
 
Torrents for FreeBSD users
 
Torrents for FreeBSD users
 +
 +
(There are no torrents at this time)
  
 
== FAQ ==
 
== FAQ ==
 +
 +
* '''How can I contribute a torrent of my OE environment, to help future OpenMoko developers jump-start their work?'''
 +
 +
That is a very excellent question, and we are very happy that you asked! Please see [[OpenEmbedded Torrent Submission]] for more details.
  
 
* '''Why does my environment rebuild gcc-cross, binutils-cross, libtool-native, ... ?'''
 
* '''Why does my environment rebuild gcc-cross, binutils-cross, libtool-native, ... ?'''
Line 27: Line 37:
 
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 [http://en.wikipedia.org/wiki/Gremlin gremlins] might attack you, your loved ones, and your town, possibly ruining Christmas for everyone.
 
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 [http://en.wikipedia.org/wiki/Gremlin gremlins] might attack you, your loved ones, and your town, possibly ruining Christmas for everyone.
  
[[Category:Application Developer]]
+
== Contributing to the Pool of Torrents ==
[[Category:System Developers]]
+
 
 +
If you have noticed that the available torrents for your architecture, machine, and distro are few (or none), then we would love it if you would share your build environment for other OpenMoko developers to get up-to-speed fast!
 +
 
 +
Please see [[OpenEmbedded Torrent Submission]] for more details.
 +
 
 +
[[Category:Developer resources]]

Latest revision as of 12:15, 19 July 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

[edit] Available Torrents

[edit] Linux Users

Torrents for Linux users

(There are no torrents at this time)

[edit] Mac OS X Users

Torrents for Mac OS X users

(There are no torrents at this time)

[edit] FreeBSD Users

Torrents for FreeBSD users

(There are no torrents at this time)

[edit] FAQ

  • How can I contribute a torrent of my OE environment, to help future OpenMoko developers jump-start their work?

That is a very excellent question, and we are very happy that you asked! Please see OpenEmbedded Torrent Submission for more details.

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

[edit] Contributing to the Pool of Torrents

If you have noticed that the available torrents for your architecture, machine, and distro are few (or none), then we would love it if you would share your build environment for other OpenMoko developers to get up-to-speed fast!

Please see OpenEmbedded Torrent Submission for more details.

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.