Starting jhbuild – Installation

Step 1.-

To install Jhbuild in Fedora15, you must be sure that you have installed python in your computer. The most commonly avaible python versions are: 2.7.1 and 3.2, so I did checked the version in /usr/bin.  * To understand better this step, see the figure 1 below.

Step 2.-

Create a directory where you can download jhbuild. In this case we are going to create the “gnome” directory: mkdir gnome. Make sure you are on the rigth directory (the current directory is the directory you want to stay). cd gnome

*To understand better this step, see the figure 1 below.

Step 3.-

Install Jhbuild via Git.  *To understand better this step, see the figure 1 below.

[yulys@yulys gnome]$ git clone git://git.gnome.org/jhbuild

Step 4.-

We are going to list the files into the gnome directory to see a folder named jhbuild after installing: ls. Finally we must to execute the script /autogen.sh [1]

*To understand better this step, see the figure 1 below.

Figure 1.-

As you can see, the installation requires many packages like autoconf, automake, libtool, gettex, intltools, pkg-config; but here we have a little problem… the installation can’t find the gnome-doc-utils packages… don’t worry it says also the way to solve:

***Error***: You must have gnome-doc-utils >= 0.4.2 installed
to build jhbuild.  Download the appropriate package for
from your distribution or get the source tarball at
http://ftp.gnome.org/pub/GNOME/sources/gnome-doc-utils/

* I did installed unsuccessfully gnome-doc-utils-0.20.2, gnome-doc-utils-0.20.6 and gnome-doc-utils-0.20.6-1.fc15.noarch.rpm, because the same message appeared again and again…

* Note: If libtool is missing, you will need it soon, anyway. “jhbuild bootstrap” may help you there, but you can easily install it from your system, if needed (# yum install libtool) [2]

* uhmmm what I finally did was the second part of the message recommended:

Note that autotools are only required to build documentation;
type make -f Makefile.plain to build or install JHBuild without
the documentation

So I type the commands make -file Makefile.plain, then make-file Makefile.plain install:

Figure 2.-

Step 5.-

Now we are going to check the smalls shell script installed in jhbuild. First we have into /jhbuild/jhbuild the default.jhbuildrc file; and other examples into /jhbuild/examples.

Figure 3.-

Step 6.-

Set the $PATH and $HOME environment variables with single quotes, because you or your system can add or remove folders to them elsewhere (on ~/.profile, ~/.bash_profile, /etc/bash.bashrc), using an literal $PATH instead of taking its value right now is better to keep your system working, with no surprises. Also it’s preferably in this case to use $HOME instead of ~, for readability. $HOME is an environment variable that holds the location of your home folder as a string. ~ is kind of a shortcut for it, useful for command line use, but prefer readability for scripts. [2]

* We realized that the path for jhbuild file is $HOME/.local/bin, so we are going to type:

[yulys@yulys examples]$ echo ‘export PATH=$PATH:$HOME/.local/bin’ >> ~/.bashrc

… I found the file .bashrc in root:

[root@yulys /]# cd root
 [root@yulys ~]# ls -a
 .   anaconda-ks.cfg  .bash_logout   .bashrc  .ccache  .cshrc  .gconf   .gstreamer-0.10  install.log.syslog  .local   .xauthPI5zCu
 ..  .bash_history    .bash_profile  .cache   .config  .dbus   .gconfd  install.log      .lesshst            .tcshrc
 [root@yulys ~]# gedit .bashrc

Sources:

[1] http://live.gnome.org/Jhbuild

[2]From the  Asrail’ comment

About Julita Inca

Ingeniero de Sistemas UNAC, Magíster en Ciencias de la Computación PUCP, OPW GNOME 2011, Miembro de la GNOME Foundation desde el 2012, Embajadora Fedora Perú desde el 2012, ganadora del scholarship of the Linux Foundation 2012, experiencia como Admin Linux en GMD y Especialista IT en IBM, con certificaciones RHCE, RHCSA, AIX 6.1, AIX 7 Administrator e ITILv3. Experiencia académica en universidades como PUCP, USIL y UNI. HPC researcher, a simple mortal, like you!
This entry was posted in GNOME and tagged , , , , , , . Bookmark the permalink.

10 Responses to Starting jhbuild – Installation

  1. smartass says:

    do not run jhbuild as root

  2. Is there a specific reason why you don’t use jhbuild as a normal user but as root (if I understood it correctly)?

  3. diega says:

    hi,
    you can find a few samples of .jhbuildrc files into the sources of jhbuild[0]. They have pretty nice comments so should be easy to adjust them to your needs. jhbuild will look into the root of your home folder for a file named .jhbuildrc. Also you can use the -f option to specify a different file (useful in case you have many jhbuild environments).
    HTH.
    Regards.

    [0]: http://git.gnome.org/browse/jhbuild/tree/examples

  4. Asrail says:

    Hi,

    first, you have autotools, as you could see by having automake and autoconf. If libtool is missing, you will need it soon, anyway. “jhbuild bootstrap” may help you there, but you can easily install it from your system, if needed (# yum install libtool)

    Second, there is an example on jhbuild/example/, ending in .jhbuildrc. Reads its comments, copy on ~/.jhbuildrc and edit as you desire.

    • Julita Inca says:

      Thanks Mister Asrail!
      The second part of your comment made me see the light, I have already check the file “ending with .jhbuilrc”:sample.jhbuildrc. So I don’t need to rewrite my article, I will only change the pics where I can show the access as a user instead of root.🙂

  5. Asrail says:

    Just another tip,

    instead of doing:
    echo PATH=$PATH:~/.local/bin >> ~/.bashrc

    you should do:
    echo ‘export PATH=$PATH:$HOME/.local/bin’ >> ~/.bashrc

    or edit the .bashrc and add the quoted region.

    With the single quotes instead of double quotes it won’t expand the values ($PATH, $HOME). Also, since you or your system can add or remove folders to the $PATH environment variable elsewhere (on ~/.profile, ~/.bash_profile, /etc/bash.bashrc), using an literal $PATH instead of taking its value right now is better to keep your system working, with no surprises.
    Also it’s preferably in this case to use $HOME instead of ~, for readability. $HOME is an environment variable that holds the location of your home folder as a string. ~ is kind of a shortcut for it, useful for command line use, but prefer readability for scripts.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s