Difference between revisions of "JHBuild"

From ArchWiki
Jump to: navigation, search
(Troubleshooting: This was fixed)
(Installation: link install page)
 
(79 intermediate revisions by 13 users not shown)
Line 1: Line 1:
 
[[Category:Development]]
 
[[Category:Development]]
JHBuild is a tool that allows you to automatically download and compile "modules" (i.e. source code packages). It can pull modules from a variety of sources (CVS, Subversion, Git, Bazaar, tarballs...) and handle dependencies. You can also choose which specific modules you want to build, instead of building the whole project.
+
[[ja:JHBuild]]
 +
JHBuild is a tool that allows you to automatically download and compile "modules" (i.e. source code packages). It can pull modules from a variety of sources (CVS, Subversion, Git, Bazaar, tarballs, etc.) and handle dependencies. You can also choose which specific modules you want to build, instead of building the whole project.
  
 
JHBuild was originally written for building [[GNOME]], but has since been extended to be usable with other projects.
 
JHBuild was originally written for building [[GNOME]], but has since been extended to be usable with other projects.
  
==Installation==
+
== Installation ==
  
JHBuild is available in the [[Arch User Repository]]. Install either {{AUR|jhbuild}} or {{AUR|jhbuild-git}}, the development version.
+
[[Install]] the {{AUR|jhbuild}} package.
  
==Configuration==
+
== Configuration ==
  
The configuration file for JHBuild is {{ic|~/.jhbuildrc}}. It uses [[Python]] syntax to set configuration variables. Here is the sample file provided for building GNOME:
+
JHBuild gets its configuration from a system-wide configuration file installed with the package, the {{Ic|defaults.jhbuildrc}}, and from an optional user configuration file jhbuildrc, in {{ic|~/.config/jhbuildrc}} (if it exists).
  
# -*- mode: python -*-
+
These files use [[Python]] syntax to set configuration variables.
# -*- coding: utf-8 -*-
 
 
# edit this file to match your settings and copy it to ~/.jhbuildrc
 
 
# if you have a GNOME git account, uncomment this line
 
# repos['git.gnome.org'] = 'ssh://user@git.gnome.org/git/'
 
 
# what module set should be used.  The default can be found in
 
# jhbuild/defaults.jhbuildrc, but can be any file in the modulesets directory
 
# or a URL of a module set file on a web server.
 
# moduleset = 'gnome-apps-3.2'
 
#
 
# A list of the modules to build.  Defaults to the GNOME core and tested apps.
 
# modules = [ 'meta-gnome-core', 'meta-gnome-apps-tested' ]
 
 
# Or to build the old GNOME 2.32:
 
# moduleset = 'gnome2/gnome-2.32'
 
# modules = ['meta-gnome-desktop']
 
 
# what directory should the source be checked out to?
 
checkoutroot = os.path.expanduser('~/checkout/gnome')
 
 
# the prefix to configure/install modules to (must have write access)
 
prefix = '/opt/gnome'
 
 
# custom CFLAGS / environment pieces for the build
 
# os.environ['CFLAGS'] = '-Wall -g -O0'
 
 
# extra arguments to pass to all autogen.sh scripts
 
# to speed up builds of GNOME, try '--disable-static --disable-gtk-doc'
 
#autogenargs=''
 
 
# On multiprocessor systems setting makeargs to '-j2' may improve compilation
 
# time. Be aware that not all modules compile correctly with '-j2'.
 
# Set makeargs to 'V=1' for verbose build output.
 
#makeargs = '-j2'
 
  
You should edit at least ''modules'' to the desired modules to be built. A reference for most configuration variables is available at [http://developer.gnome.org/jhbuild/unstable/config-reference.html.en GNOME JHBuild Manual].
+
The variables currently accepted can be found in [https://developer.gnome.org/jhbuild/stable/ JHBuild Manual].
  
==Usage==
+
=== Default JHBuild configuration ===
  
===Installing Prerequisites===
+
JHBuild default configuration is provided by {{AUR|jhbuild}} and can be found at {{Ic|/usr/lib/python2.7/site-packages/jhbuild/defaults.jhbuildrc}}.
  
JHBuild can check if the required tools are installed by running ''sanitycheck'':
+
{{Ic|defaults.jhbuildrc}} should contain all values for options (e.g. moduleset, module_autoargs) needed to run JHBuild smoothly.
 +
 
 +
Even though the default values in {{Ic|defaults.jhbuildrc}} should be all you need for running JHBuild, you might want to take a look at it to decide if and what you want to customize in a personal configuration file.
 +
 
 +
{{note|If you think you found a setting that should be default, feel free to suggestion that in {{AUR|jhbuild}} comments}}
 +
 
 +
=== User configuration ===
 +
 
 +
The file {{Ic|~/.config/jhbuildrc}} is optional. You can create it with your personal JHBuild configurations, in order to overlap the default values (see above topic).
 +
 
 +
A very extended sample of a configuration file can be found in {{Ic|/usr/share/jhbuild/examples/sample.jhbuildrc}}
 +
 
 +
User configuration is particularly useful to, e.g., set a different moduleset, to add a flag to a build system to debug or to disable something.
 +
 
 +
See below a few examples for {{Ic|~/.config/jhbuildrc}} contents:
 +
 
 +
* Enable a wide-most moduleset, and also force GTK3 for modules that would use GTK2 by default
 +
{{bc|<nowiki>
 +
moduleset = ['gnome-world']
 +
autogenargs = '--with-gtk3'
 +
</nowiki>}}
 +
 
 +
* Or you may want to enable documentation build for autotools, even though it will slowdown module compilation
 +
{{bc|<nowiki>
 +
autogenargs = '--enable-gtk-doc'
 +
</nowiki>}}
 +
 
 +
* Or you want some debug output from make command
 +
{{bc|<nowiki>
 +
makeargs = 'V=1'
 +
</nowiki>}}
 +
 
 +
* Or you found out that a module requires a specific automake option (WebKit is already patched, there is no real need for this one)
 +
{{bc|<nowiki>
 +
module_autogenargs['WebKit'] = 'PYTHON=/usr/bin/python2'
 +
</nowiki>}}
 +
 
 +
* Or you want to disable documentation build for a module that use meson build system
 +
{{bc|<nowiki>
 +
module_mesonargs['gstreamer'] = '-Ddisable_gtkdoc=true
 +
</nowiki>}}
 +
 
 +
{{note|'''autotools''' and '''meson''' are different build systems, so make sure to add the desired flags for the correct option name}}
 +
 
 +
== Usage ==
 +
 
 +
This topic provides some information and examples on how to use some JHBuild commands, but without intending to exhaust the subject. For a detailed information on each of JHBuild commands, please refer to [https://developer.gnome.org/jhbuild/stable/ JHBuild Manual], learn from each command's help output or even read JHBuild's [https://git.gnome.org/browse/jhbuild/ source code].
 +
 
 +
JHBuild provides a general {{Ic|--help}} which lists all the commands available, and also a help message for each sub-command, e.g. {{Ic|jhbuild sysdeps --help}}.
 +
 
 +
=== Checking and installing prerequisites ===
 +
 
 +
''sysdeps'' can be used to get a detailed list of which dependencies you have installed and which ones you should install. In order to get this information, just run:
 +
 
 +
$ jhbuild sysdeps
 +
 
 +
Alternatively, ''sanitycheck'' may also be used to report missing tools that are required (e.g. mozjs38). If nothing is reported (and exit code is 0), then you're good to go! Similiar to the above command, just run:
  
 
  $ jhbuild sanitycheck
 
  $ jhbuild sanitycheck
  
If any errors are shown, missing packages may be installed from repositories or running the ''bootstrap'' command, which tries to download, build and install the build prerequisites:
+
If some tools are reported to be missing, you can — besides installing correspondent packages with pacman, if available — run ''bootstrap'' command, which will download, build and install the named module inside your jhbuild tree:
  
 
  $ jhbuild bootstrap
 
  $ jhbuild bootstrap
  
===Building===
+
{{note|All dependencies informed by ''sysdeps'' should be already listed as dependency {{AUR|jhbuild}} by now. If you run ''sysdeps'' and find out a dependency that is not be listed, please report it in the comments of {{AUR|jhbuild}}}}
 +
 
 +
=== Updating modules ===
 +
 
 +
It is possible to simply update the source code of the modules without building them, making it possible build another time without having to wait fetching the source code. There are three ways of simply updating modules:
 +
 
 +
''update'', without any arguments, will update all modules available in the moduleset/modules set in configuration file
 +
 
 +
$ jhbuild update
 +
 
 +
''update'', with one or more modules as arguments, will update '''all''' modules that the named modules depends on. e.g.:
 +
 
 +
$ jhbuild update gedit
 +
 
 +
''updateone'', with one or more modules, will update '''only''' the named module(s). e.g.:
 +
 
 +
$ jhbuild updateonly gedit
 +
 
 +
=== Building modules ===
  
To build all the modules selected in the configuration file, just run the ''build'' command:
+
This action will run the whole build process: it will update the source code (unless it is already up-to-date), configure & build, and install it in the proper directory.
 +
 
 +
Just like ''update'', There are three ways of building modules in JHBuild:
 +
 
 +
''build'', without any arguments, will build all modules available in the moduleset/modules set in configuration file
  
 
  $ jhbuild build
 
  $ jhbuild build
  
JHBuild will download, configure, compile and install each of the modules.
+
''build'', with one or more modules as arguments, will build '''all''' modules that the named modules depends on. e.g.:
 +
 
 +
$ jhbuild build gedit
 +
 
 +
''buildone'', with one or more modules, will build '''only''' the named module(s). e.g.:
 +
 
 +
$ jhbuild buildone gedit
 +
 
 +
{{note|Please notice that since ''buildone'' don't also build the latest development version of a module's dependencies, it may fail due to dependency not being installed or being out-of-date; in this case, you should run ''build'' for the named module}}
 +
 
 +
=== Running modules ===
 +
 
 +
After a successfully installed application in JHBuild, use ''run'' to start the module you just built. e.g.:
 +
 
 +
$ jhbuild run gedit
 +
 
 +
=== Creating dependency graph ===
 +
 
 +
JHBuild can output graph contents which can by piped into {{Pkg|graphviz}} in order to generate e.g. a PNG or PostScript file.
 +
 
 +
To generate a PNG file of e.g. gedit, run:
 +
 
 +
$ jhbuild dot gedit | dot -Tpng > dependencies.png
  
If an error occurs at any stage, JHBuild will present a menu asking what to do. The choices include dropping to a shell to fix the error, rerunning the build from various stages, giving up on the module, or ignore the error and continue. Often, dropping to a shell and checking makefiles and configuration files can be helpful. If you face a build error, for example, you can try to manually {{ic|make}} and check errors on the shell.
+
== Troubleshooting ==
  
Giving up on a module will cause any modules depending on it to fail.
+
{{Note|If you encounter an issue that is not documented below, please report it in a comment on the {{AUR|jhbuild}} package.}}
  
==Troubleshooting==
+
=== Python issues ===
  
===Python issues===
+
A module that depends on {{Pkg|python2}} may fail to build as softwares usually expect the binary filename of python 2.x to be {{Ic|/usr/bin/python}} and python 3.x to be {{Ic|/usr/bin/python3}}, which is not the case in Arch Linux: python 2.x is {{Ic|/usr/bin/python2}} and python 3.x is {{Ic|/usr/bin/python}}.
  
==== "error: Python interpreter is too old" ====
+
For cases like that, force the modules to run {{Ic|/usr/bin/python2}} using the one or more methods below:
  
You may get the following error when building various modules:
+
* set ''module_autoargs'' with ''PYTHON=/usr/bin/python2'' for this specific module in {{Ic|~/.config/jhbuildrc}}, as mentioned in the above Configuration section — this will run autogen.sh or configure with this value for variable PYTHON  
checking for Python 3 availability.... checking whether /usr/bin/python2 version is >= 3.2.0... no
 
configure: error: Python interpreter is too old
 
To work around this issue, choose {{ic|[4] Start shell}}. Then, find the {{ic|autogen.sh}} command, which should look something like
 
Running ./configure --enable-maintainer-mode --prefix /home/kerrick/.jhbuild/install --libdir /home/kerrick/.jhbuild/install/lib64 --enable-python3 --disable-static --disable-gtk-doc PYTHON=/usr/bin/python2 ...
 
Run this autogen.sh command, but remove the {{ic|PYTHON&#61;/usr/bin/python2}} portion. Then, exit the shell, and choose {{ic|[2] Ignore error and continue to build}}.
 
  
====Building from scratch without JHBuild, or in a JHBuild shell====
+
* if the ''configure'' or ''Makefile'' doesn't parse PYTHON variable, one approach is to manually find all lines in ''configure''/''Makefile'' that run python binary and rename python -> python2 — this will hard code python2 in the module's source code.
  
If you are building from scratch on your own, it may be necessary to run autogen.sh with the following:
+
* if only the above workarounds still don't work for you, consider editing module's .py files in order to replace ''python'' with ''python2'' when the first line matches ''#!/usr/bin/env python'' or ''#!/usr/bin/python''
  
PYTHON=/usr/bin/python2 ./autogen.sh
+
{{note|All edits and patches that are manually applied to the source code will be lost when you wipe the directory and checkout (download) it again, so it is not exactly a permanent solution}}
  
The shebang line in ~/.local/bin/jhbuild may need to be updated to:
+
{{note|If a module's configure/build process misuse PYTHON variable, or doesn't use at all, consider reporting it to the module's upstream and/or providing patch for JHBuild upstream}}
#!/usr/bin/python2
 
  
You may need to switch the symlink "/usr/bin/python" to point to python2.7 to get "jhbuild build" to run correctly. The folks in #gnome-shell on irc.gnome.org will help in any way they can.
+
==== Modules known to require python2 exclusively ====
 +
 
 +
{{AUR|jhbuild}} is already patched to use ''python2'' for modules that exclusively require this Python version, and therefore no action is required if you're using packaged JHBuild.
 +
 
 +
They are:
 +
* telepathy-mission-control
 +
* WebKit
  
 
=== pkg-config issues ===
 
=== pkg-config issues ===
If you have a malformatted .pc file on your PKG_CONFIG_PATH, JHBuild won't be able to detect all the (valid) .pc files you have installed and will complain that the .pc files are missing. Look at the output of {{ic|jhbuild sysdeps}}—there should be a message about the problematic .pc files.
 
  
=== libquvi configure fails ===
+
If you have a malformatted .pc file on your PKG_CONFIG_PATH, JHBuild will not be able to detect all the (valid) .pc files you have installed and will complain that the .pc files are missing. Look at the output of {{ic|jhbuild sysdeps}}—there should be a message about the problematic .pc files.
Choose {{ic|[4] Start shell}} and run
+
 
git checkout next
+
=== Build failed due to incompatible meson versions ===
then choose {{ic|[7] Go to phase "configure"}}.
+
 
 +
You may come across with a message similar to the one below.
 +
 
 +
{{bc|
 +
Meson encountered an error:
 +
Build directory has been generated with Meson version 0.40.0, which is incompatible with current version 0.40.1.
 +
Please delete this build directory AND create a new one.
 +
FAILED: build.ninja
 +
'/usr/bin/python3' '/home/foobar/jhbuild/install/bin/meson' --internal regenerate '/home/foobar/jhbuild/checkout/gst-plugins-base' '/home/foobar/.cache/jhbuild/build/gst-plugins-base' --backend ninja
 +
ninja: error: rebuilding 'build.ninja': subcommand failed}}
 +
 
 +
In the above example, the module was configured with meson 0.40.0 at on time, but a newer version (0.40.1, in the example) is now installed and is not compatible with the old one.
 +
 
 +
'''Solution:''' Run Configure phase again, in order to have this module configured with newer Meson version
 +
 
 +
== Building JHBuild from scratch ==
 +
 
 +
If you do not want to use the {{AUR|jhbuild}} package, and instead you want build JHBuild from scratch on your own, there are a few things you should pay attention too.
 +
 
 +
* Make sure to install all the dependencies required by JHBuild and its target modules. Refer to [https://wiki.gnome.org/Projects/Jhbuild/Dependencies/ArchLinux list of dependencies for Arch Linux];
  
=== libquvi-scripts configure fails ===
+
* JHBuild itself depends on [[Python]] version 2, so make sure to run JHBuild's ''autogen.sh'' with the following command line:
Choose {{ic|[4] Start shell}} and run
 
git checkout next
 
Then, copy the configure command line from the terminal scrollback and run it (it starts with {{ic|./bootstrap.sh && ./configure}}). Then, exit the shell and choose {{ic|[2] Ignore error and continue to build}}.
 
  
=== totem doesn't build ===
+
$ PYTHON=/usr/bin/python2 ./autogen.sh
Choose {{ic|[4] Start shell}} and run
 
curl https://git.gnome.org/browse/totem/patch/?id=198d7f251e7816f837378fb2081829188847b916 | git apply
 
Then, exit the shell and choose {{ic|[1] Rerun phase build}}.
 
  
=== evolution doesn't build ===
+
* Likewise, some modules may still depend on python2. Make sure to read the above topic 'Python issues'.
Choose {{ic|[4] Start shell}} and run
 
curl https://bug707112.bugzilla-attachments.gnome.org/attachment.cgi?id=253584 | git apply
 
Then, exit the shell and choose {{ic|[1] Rerun phase build}}. See [https://bugzilla.gnome.org/show_bug.cgi?id=707112 this bug] for further details.
 
  
=== Other broken modules ===
+
* For detailed information downloading and building the source code of JHBuild, check [https://wiki.gnome.org/HowDoI/JhbuildJHBuild's "How Do I" at GNOME wiki].
The following modules don't build, and there are no known fixes:
 
* devhelp—[https://bugzilla.gnome.org/show_bug.cgi?id=707107 bug report]
 
* ibus-pinyin
 
* aisleriot—[https://bugzilla.gnome.org/show_bug.cgi?id=707106 bug report] (probably easy to fix if you poke around)
 
  
==External links==
+
== See also ==
  
[http://developer.gnome.org/jhbuild/ GNOME JHBuild Manual]
+
* [https://wiki.gnome.org/Projects/Jhbuild JHBuild homepage in GNOME Wiki]
 +
* [https://wiki.gnome.org/Newcomers/BuildGnome JHBuild for GNOME newcomers]
 +
* [https://wiki.gnome.org/HowDoI/Jhbuild JHBuild for experienced GNOME contributors]
 +
* [https://developer.gnome.org/jhbuild/stable/ JHBuild Manual]
 +
* [https://git.gnome.org/browse/jhbuild/ JHBuild Source Code]

Latest revision as of 20:41, 11 May 2017

JHBuild is a tool that allows you to automatically download and compile "modules" (i.e. source code packages). It can pull modules from a variety of sources (CVS, Subversion, Git, Bazaar, tarballs, etc.) and handle dependencies. You can also choose which specific modules you want to build, instead of building the whole project.

JHBuild was originally written for building GNOME, but has since been extended to be usable with other projects.

Installation

Install the jhbuildAUR package.

Configuration

JHBuild gets its configuration from a system-wide configuration file installed with the package, the defaults.jhbuildrc, and from an optional user configuration file jhbuildrc, in ~/.config/jhbuildrc (if it exists).

These files use Python syntax to set configuration variables.

The variables currently accepted can be found in JHBuild Manual.

Default JHBuild configuration

JHBuild default configuration is provided by jhbuildAUR and can be found at /usr/lib/python2.7/site-packages/jhbuild/defaults.jhbuildrc.

defaults.jhbuildrc should contain all values for options (e.g. moduleset, module_autoargs) needed to run JHBuild smoothly.

Even though the default values in defaults.jhbuildrc should be all you need for running JHBuild, you might want to take a look at it to decide if and what you want to customize in a personal configuration file.

Note: If you think you found a setting that should be default, feel free to suggestion that in jhbuildAUR comments

User configuration

The file ~/.config/jhbuildrc is optional. You can create it with your personal JHBuild configurations, in order to overlap the default values (see above topic).

A very extended sample of a configuration file can be found in /usr/share/jhbuild/examples/sample.jhbuildrc

User configuration is particularly useful to, e.g., set a different moduleset, to add a flag to a build system to debug or to disable something.

See below a few examples for ~/.config/jhbuildrc contents:

  • Enable a wide-most moduleset, and also force GTK3 for modules that would use GTK2 by default
 moduleset = ['gnome-world']
 autogenargs = '--with-gtk3'
  • Or you may want to enable documentation build for autotools, even though it will slowdown module compilation
 autogenargs = '--enable-gtk-doc'
  • Or you want some debug output from make command
 makeargs = 'V=1'
  • Or you found out that a module requires a specific automake option (WebKit is already patched, there is no real need for this one)
 module_autogenargs['WebKit'] = 'PYTHON=/usr/bin/python2'
  • Or you want to disable documentation build for a module that use meson build system
 module_mesonargs['gstreamer'] = '-Ddisable_gtkdoc=true
Note: autotools and meson are different build systems, so make sure to add the desired flags for the correct option name

Usage

This topic provides some information and examples on how to use some JHBuild commands, but without intending to exhaust the subject. For a detailed information on each of JHBuild commands, please refer to JHBuild Manual, learn from each command's help output or even read JHBuild's source code.

JHBuild provides a general --help which lists all the commands available, and also a help message for each sub-command, e.g. jhbuild sysdeps --help.

Checking and installing prerequisites

sysdeps can be used to get a detailed list of which dependencies you have installed and which ones you should install. In order to get this information, just run:

$ jhbuild sysdeps

Alternatively, sanitycheck may also be used to report missing tools that are required (e.g. mozjs38). If nothing is reported (and exit code is 0), then you're good to go! Similiar to the above command, just run:

$ jhbuild sanitycheck

If some tools are reported to be missing, you can — besides installing correspondent packages with pacman, if available — run bootstrap command, which will download, build and install the named module inside your jhbuild tree:

$ jhbuild bootstrap
Note: All dependencies informed by sysdeps should be already listed as dependency jhbuildAUR by now. If you run sysdeps and find out a dependency that is not be listed, please report it in the comments of jhbuildAUR

Updating modules

It is possible to simply update the source code of the modules without building them, making it possible build another time without having to wait fetching the source code. There are three ways of simply updating modules:

update, without any arguments, will update all modules available in the moduleset/modules set in configuration file

$ jhbuild update

update, with one or more modules as arguments, will update all modules that the named modules depends on. e.g.:

$ jhbuild update gedit

updateone, with one or more modules, will update only the named module(s). e.g.:

$ jhbuild updateonly gedit

Building modules

This action will run the whole build process: it will update the source code (unless it is already up-to-date), configure & build, and install it in the proper directory.

Just like update, There are three ways of building modules in JHBuild:

build, without any arguments, will build all modules available in the moduleset/modules set in configuration file

$ jhbuild build

build, with one or more modules as arguments, will build all modules that the named modules depends on. e.g.:

$ jhbuild build gedit

buildone, with one or more modules, will build only the named module(s). e.g.:

$ jhbuild buildone gedit
Note: Please notice that since buildone don't also build the latest development version of a module's dependencies, it may fail due to dependency not being installed or being out-of-date; in this case, you should run build for the named module

Running modules

After a successfully installed application in JHBuild, use run to start the module you just built. e.g.:

$ jhbuild run gedit

Creating dependency graph

JHBuild can output graph contents which can by piped into graphviz in order to generate e.g. a PNG or PostScript file.

To generate a PNG file of e.g. gedit, run:

$ jhbuild dot gedit | dot -Tpng > dependencies.png

Troubleshooting

Note: If you encounter an issue that is not documented below, please report it in a comment on the jhbuildAUR package.

Python issues

A module that depends on python2 may fail to build as softwares usually expect the binary filename of python 2.x to be /usr/bin/python and python 3.x to be /usr/bin/python3, which is not the case in Arch Linux: python 2.x is /usr/bin/python2 and python 3.x is /usr/bin/python.

For cases like that, force the modules to run /usr/bin/python2 using the one or more methods below:

  • set module_autoargs with PYTHON=/usr/bin/python2 for this specific module in ~/.config/jhbuildrc, as mentioned in the above Configuration section — this will run autogen.sh or configure with this value for variable PYTHON
  • if the configure or Makefile doesn't parse PYTHON variable, one approach is to manually find all lines in configure/Makefile that run python binary and rename python -> python2 — this will hard code python2 in the module's source code.
  • if only the above workarounds still don't work for you, consider editing module's .py files in order to replace python with python2 when the first line matches #!/usr/bin/env python or #!/usr/bin/python
Note: All edits and patches that are manually applied to the source code will be lost when you wipe the directory and checkout (download) it again, so it is not exactly a permanent solution
Note: If a module's configure/build process misuse PYTHON variable, or doesn't use at all, consider reporting it to the module's upstream and/or providing patch for JHBuild upstream

Modules known to require python2 exclusively

jhbuildAUR is already patched to use python2 for modules that exclusively require this Python version, and therefore no action is required if you're using packaged JHBuild.

They are:

  • telepathy-mission-control
  • WebKit

pkg-config issues

If you have a malformatted .pc file on your PKG_CONFIG_PATH, JHBuild will not be able to detect all the (valid) .pc files you have installed and will complain that the .pc files are missing. Look at the output of jhbuild sysdeps—there should be a message about the problematic .pc files.

Build failed due to incompatible meson versions

You may come across with a message similar to the one below.

Meson encountered an error:
Build directory has been generated with Meson version 0.40.0, which is incompatible with current version 0.40.1.
Please delete this build directory AND create a new one.
FAILED: build.ninja 
'/usr/bin/python3' '/home/foobar/jhbuild/install/bin/meson' --internal regenerate '/home/foobar/jhbuild/checkout/gst-plugins-base' '/home/foobar/.cache/jhbuild/build/gst-plugins-base' --backend ninja
ninja: error: rebuilding 'build.ninja': subcommand failed

In the above example, the module was configured with meson 0.40.0 at on time, but a newer version (0.40.1, in the example) is now installed and is not compatible with the old one.

Solution: Run Configure phase again, in order to have this module configured with newer Meson version

Building JHBuild from scratch

If you do not want to use the jhbuildAUR package, and instead you want build JHBuild from scratch on your own, there are a few things you should pay attention too.

  • JHBuild itself depends on Python version 2, so make sure to run JHBuild's autogen.sh with the following command line:
$ PYTHON=/usr/bin/python2 ./autogen.sh
  • Likewise, some modules may still depend on python2. Make sure to read the above topic 'Python issues'.

See also