Development Team/Manual/Setup: Difference between revisions

No edit summary
 
(One intermediate revision by one other user not shown)
Line 3: Line 3:


[[Image:Sugar.png|right|thumb|Sugar GUI Shell (Our Goal)]]
[[Image:Sugar.png|right|thumb|Sugar GUI Shell (Our Goal)]]
The OLPC's software environment is a heavily modified [[Community/Distributions/Fedora| Fedora]] 11 Linux system running a custom [[Sugar|GUI shell]] (Sugar).  To develop for the platform you will eventually need access to a platform which runs in a manner substantially similar to the OLPC environment.  To put it simply, you will likely need to have Sugar running on a computer.
The OLPC's software environment is a heavily modified [[Fedora]] 11 Linux system running a custom [[Sugar|GUI shell]] (Sugar).  To develop for the platform you will eventually need access to a platform which runs in a manner substantially similar to the OLPC environment.  To put it simply, you will likely need to have Sugar running on a computer.


There are two major approaches to running Sugar, running it natively on your machine, and running it in an emulated environment.  Which approach you choose will depend on a number of factors, including:
There are two major approaches to running Sugar, running it natively on your machine, and running it in an emulated environment.  Which approach you choose will depend on a number of factors, including:
Line 140: Line 140:
This is what the core development team uses and is one of the most pleasant ways to work (once set up). Compared with using an Emulated XO, installing sugar takes more time and space to set up, and can be difficult to maintain, but results in a more flexible environment.
This is what the core development team uses and is one of the most pleasant ways to work (once set up). Compared with using an Emulated XO, installing sugar takes more time and space to set up, and can be difficult to maintain, but results in a more flexible environment.


The 'native' environment for sugar-jhbuild is [[Community/Distributions/Fedora|Fedora]], and this is by far the best supported development platform for sugar-jhbuild. [[Community/Distributions/Ubuntu|Ubuntu]] and [[Community/Distributions/Gentoo|Gentoo]] can also build the environment.
The 'native' environment for sugar-jhbuild is [[Fedora]], and this is by far the best supported development platform for sugar-jhbuild. [[Ubuntu]] and [[Gentoo]] can also build the environment.


Currently sugar-jhbuild requires about 2.5 hours to complete building on a modern workstation (AMD4800+).
Currently sugar-jhbuild requires about 2.5 hours to complete building on a modern workstation (AMD4800+).
Line 156: Line 156:
As Sugar stabilizes and is ported to more distributions, it should be possible to use your Linux distribution's package management system to install Sugar.  Distributions with ports so far:
As Sugar stabilizes and is ported to more distributions, it should be possible to use your Linux distribution's package management system to install Sugar.  Distributions with ports so far:


* [[Community/Distributions/Ubuntu]] -- These packages seem to work well and are extremely easy to set up.  If you are running on Ubuntu Gutsy and are not working on Sugar's core software, this is very simple way to work.
* [[Ubuntu]] -- These packages seem to work well and are extremely easy to set up.  If you are running on Ubuntu Gutsy and are not working on Sugar's core software, this is very simple way to work.
* [[Community/Distributions/Debian]]-- Note that we need more testing of this package-set, please let us know your experiences
* [[Debian]]-- Note that we need more testing of this package-set, please let us know your experiences




Line 215: Line 215:
* [[Activities]] -- can be downloaded using the built-in browser or installed from the command line
* [[Activities]] -- can be downloaded using the built-in browser or installed from the command line
* General Linux packages can be downloaded and installed using Yum (note, these changes will be wiped out on the next OS upgrade)
* General Linux packages can be downloaded and installed using Yum (note, these changes will be wiped out on the next OS upgrade)
=== Jabber Servers ===
By default your image may have been configured to connect to either an inaccessible or a non-existent Jabber server.  You can see this by zooming out to the network view (Alt-F1 in an emulator).  If there are no other XO icons in the view you are likely not connecting to a server.
At the moment (2007-12-17) we are in the middle of rebuilding the Jabber servers to support the much larger loads seen during deployment.  Ask on the #olpc IRC channel which Jabber server you should use, then open a [[OLPC:Terminal]] activity and use the following command:
sugar-control-panel -s jabber jabber.server.url
and then restart the X server, either restart the machine or use ctrl-alt-backspace (erase), but do '''not''' do ctrl-alt-backspace on an emulator, or you will kill your entire GUI session!


=== SSH Access ===
=== SSH Access ===