Line 6: |
Line 6: |
| ==Compatible Platforms== | | ==Compatible Platforms== |
| | | |
− | Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux Distributions which are known to work with it. | + | Jhbuild is quite demanding with regard to the packages and setup for the host Linux distribution. As a result there are only a few Linux distributions which are known to work with it. |
| | | |
− | Distros supported by the development community are Debian unstable, Fedora Rawhide, Fedora 10, and Ubuntu 8.10. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps).
| + | See the distribution specific instructions for information about whether your distribution is currently supported. Other distros which have a recent-enough release (e.g. including the latest stable GNOME release) can be supported if someone is willing to maintain the dependencies for that distro release (in config/sysdeps). |
| | | |
− | ''' Note that Debian Unstable and derived distros (e.g. Ubuntu Intrepid) contain a bug in python-gnome that impedes running jhbuild '''
| + | ==Check distro-specific instructions== |
| | | |
− | To work around this use chrpath to remove the rpath setting from your system's gconf.so:
| + | Many distributions have some quirks that need to be catered for and there are different package managing tools in use, so please check the page for your distribution before proceeding: |
| | | |
− | sudo aptitude install chrpath
| + | * [[/Debian]] |
− | find /usr/lib/python-support/python-gnome2/python2.5/gtk-2.0 -name "*.so" | sudo xargs chrpath -d
| + | * [[/Fedora]] |
| + | * [[/Ubuntu]] |
| | | |
− | ==Checkout sugar-jhbuild== | + | ==Check out sugar-jhbuild== |
| | | |
| In a suitable directory, execute | | In a suitable directory, execute |
Line 38: |
Line 39: |
| | | |
| Some tips: | | Some tips: |
− | * You may have some issues with penguintv on ubuntu, just interrupt the pull with a CTRL+C, open a shell, repeat the command manually, and accept the certificate permanently.
| |
| * hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again. | | * hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to <code>rm -rf ~/sugar-jhbuild/source/hulahop</code> and then run update and build again. |
| | | |
− | ==== Debian ====
| + | == Run Sugar == |
− | On Debian-based distros, you can use this invocation to install all dependencies automatically:
| |
− | | |
− | ./sugar-jhbuild depscheck -s | sudo xargs aptitude -y install
| |
− | | |
− | ==== Fedora ====
| |
− | | |
− | Fedora dependencies (to be installed before going through the jhbuild process) are [http://wiki.laptop.org/go/Sugar_on_Fedora#Step_1:_Install_the_build_prerequisites listed here].
| |
− | | |
− | ==Run Sugar== | |
| | | |
| This command launches the Sugar emulator: | | This command launches the Sugar emulator: |
Line 58: |
Line 49: |
| To exit the emulator, press Alt-Q. | | To exit the emulator, press Alt-Q. |
| | | |
− | == Running multiple instances== | + | == Running multiple instances == |
| To run multiple instances of sugar you can start it in the following way: | | To run multiple instances of sugar you can start it in the following way: |
| | | |