MeeGo - JHBuild
===============================================================================

meego-jhbuid is a repository containing scripts and a JHBuild moduleset for
building and developing the MeeGo 2.0 User Shell and related libraries.


Initialization
-------------------------------------------------------------------------------

You should check out JHBuild from the GNOME Git repository:

  git clone git://git.gnome.org/jhbuild

Then build it and install it.

From within the meego-jhbuild repository run:

  make install

This command will install:

  - jhbuild-meego                  - a wrapper around jhbuild
  - $HOME/.jhbuildrc-meego         - a jhbuild configuration file
  - $HOME/.jhbuildrc-meego-custom  - a jhbuild configuration file for overriding 
                                     important default settings


Building the MeeGo shell
-------------------------------------------------------------------------------

To build the whole MeeGo UI:

  jhbuild-meego build

This will build the default target, meta-meego, and its dependencies.

The modules will be downloaded to $HOME/meego/source
The modules will be installed under $HOME/meego/install

You can change the default directory by editing $HOME/.jhbuildrc-meego-custom
and editing checkoutroot and prefix.

If you want to build as little as possible, and system libraries instead
of building all the required dependencies, you can build just the 
MeeGo parts with:

  jhbuild-meego build --ignore-suggests

*** You'll need a fairly recent distro, e.g. one with a very recent GNOME,
    to do this.

Other options are available to build single modules, or specific groups of
modules. To see the available commands, run:

  jhbuild-meego --help

More information about jhbuild is available in the manual:

  http://library.gnome.org/devel/jhbuild/stable/


Launching the MeeGo shell
-------------------------------------------------------------------------------

To launch the MeeGo shell under Xephyr you should start Xephyr using:

  Xephyr :1 -screen 1024x600 -host-cursor -ac

Then enter the shell using:

  jhbuild-meego shell

And run the start-in-xephyr.sh script:

  /path/to/meego-jhbuild/build/launch-in-xephyr.sh

Or use the 'run' command:

  jhbuild-meego run /path/to/meego-jhbuild/build/launch-in-xephyr.sh


Common issues
-------------------------------------------------------------------------------

Q: Why can't jhbuild find the meego.modules file?
A: If jhbuild cannot find the meego.modules file you should edit the
jhbuildrc-meego configuration file and change the

  moduleset

or

  modulesets_dir

variables. Using an absolute path usually works.

Q: Some modules won't build because my autotools (or other build tools) are too old;
and more recent packages aren't available for my system. What can I do to upgrade them?
A: Some modules may demand particular minimum versions of autotools before
they allow themselves to be built. To ensure your jhbuild environment
has the right tools, do:

  jhbuild-meego sanitycheck

If it reports you have the wrong versions of certain tools, use:

  jhbuild-meego bootstrap

This will install all the required build tools for jhbuild.

Q: Why doesn't libsocialweb (com.intel.libsocialweb D-Bus service) start?
A: In order to activate a D-Bus service installed within the JHBuild
root you have to modify the /etc/dbus-1/session.conf file by adding
the following line:

  <servicedir>/path/to/meego-jhbuild/install/share/dbus-1/services</servicedir>

You will have to restart D-Bus, which usually means logging out or a
complete reboot.

Q: Why doesn't jhbuild pick up local changes to the meego.modules file?
A: If you modify the moduleset file locally you will need to edit the
$HOME/.jhbuildrc-meego file and change the 'moduleset' value.

Q: Why doesn't jhbuild pick up remote changes to the meego.modules file?
A: You will probably have to remove the cached meego.modules inside:

  $HOME/.cache/jhbuild

and edit the index.xml file in the same directory.

Q: When I try to build module X, it depends on a package not defined in
the moduleset. What should I do?
A: The moduleset defined for MeeGo stops roughly at the boundary between
the desktop and underlying system libraries. So, for example, it won't
attempt to build wireless-tools or hardware drivers. However, the chain
of dependencies may lead down to those libraries. To resolve this, you
should install the development headers for required system libraries
directly on the base system.


Tips
-------------------------------------------------------------------------------

If you need to override a module definition (e.g. you want a later version 
than the one specified in the GNOME moduleset), you can specify your version 
in meego.modules. As the GNOME moduleset is included by meego.modules, 
your definition is given precedence over the one from the included moduleset.