Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
xfce:building [2019/06/22 12:13]
skunnyk [Package specific dependencies]
xfce:building [2019/09/08 01:49] (current)
kevinbowen [From the code repository]
Line 1: Line 1:
-====== Building Xfce ======+====== Building Xfce from source ​======
  
 To compile a complete Xfce desktop from source requires some information about the dependency chain and the various configure options available in each module. This page will describe this in detail, so you can compile your own Xfce desktop; both system wide as well as in your $HOME directory. To compile a complete Xfce desktop from source requires some information about the dependency chain and the various configure options available in each module. This page will describe this in detail, so you can compile your own Xfce desktop; both system wide as well as in your $HOME directory.
  
-====== Version ======+  * **[[building#​Choosing your Xfce version|Choosing your Xfce version]]** 
 +  * **[[building#​Obtaining the Xfce source code|Obtaining the Xfce source code]]** 
 +  * **[[building#​Xfce dependencies explained|Xfce dependencies explained]]** 
 +  * **[[building#​Building the packages|Building the packages]]** 
 +  * **[[building#​Finding additional help|Finding additional help]]** 
 + 
 +===== Choosing your Xfce version ​=====
  
 First you will need to decide on which version of Xfce that you want to compile. Xfce version numbers are constructed like this: 1.2.3 => major.minor.micro. If the minor version is an even number, this means that it is a stable release. An odd numbered minor version indicate a development,​ or testing snapshots. The micro number increases with each release. Also, it is recommended to keep the major.minor version the same for the core components (some packages don't follow those numbers) or there will most likely be dependency version problems during compilation. First you will need to decide on which version of Xfce that you want to compile. Xfce version numbers are constructed like this: 1.2.3 => major.minor.micro. If the minor version is an even number, this means that it is a stable release. An odd numbered minor version indicate a development,​ or testing snapshots. The micro number increases with each release. Also, it is recommended to keep the major.minor version the same for the core components (some packages don't follow those numbers) or there will most likely be dependency version problems during compilation.
Line 9: Line 15:
 The latest releases available can be found on the [[http://​xfce.org/​download|download]] page. You can also build from the source repositories if you have enough experience. Additional information about this is provided below. The latest releases available can be found on the [[http://​xfce.org/​download|download]] page. You can also build from the source repositories if you have enough experience. Additional information about this is provided below.
  
-====== Source ======+===== Obtaining the Xfce source code =====
  
 Once you have decided which version that you want to compile, there are a couple of ways to download the source code. You can either choose to build official released packages, or clone the source repositories. Choosing the released packages is the recommended option. The source repositories could possibly be broken and are not generally suitable for production environments. However, they always contains the latest features, bug fixes and translations. Once you have decided which version that you want to compile, there are a couple of ways to download the source code. You can either choose to build official released packages, or clone the source repositories. Choosing the released packages is the recommended option. The source repositories could possibly be broken and are not generally suitable for production environments. However, they always contains the latest features, bug fixes and translations.
  
-If your are not sure what to choose, it is easiest to begin with the latest stable fat-tarball of a collection release.+If your are not sure which to choose, it is easiest to begin with the latest stable fat-tarball of a collection release.
  
-===== Released packages ​=====+==== Released packages ====
  
-Xfce packages have two types of releases. Click the links, below, to open the the download locations.+Xfce packages have two types of releases: collection releases and individual ​releases. Click the links, below, to open the download locations.
  
   * [[http://​archive.xfce.org/​xfce/​|Collection releases of the core modules]]\\ From time to time a new collection release of Xfce is made. A collection release consists of a number of individual tarballs and a fat-tarball that contains all of the individual tarballs.\\ The collection releases always contains the correct versions needed to build the other packages in the release. If you want the latest version of each package, you can start with a collection release and then look for individual bug fix releases, explained in the item below. ​   * [[http://​archive.xfce.org/​xfce/​|Collection releases of the core modules]]\\ From time to time a new collection release of Xfce is made. A collection release consists of a number of individual tarballs and a fat-tarball that contains all of the individual tarballs.\\ The collection releases always contains the correct versions needed to build the other packages in the release. If you want the latest version of each package, you can start with a collection release and then look for individual bug fix releases, explained in the item below. ​
   * [[http://​archive.xfce.org/​src/​xfce/​|Individual releases]]\\ Each package in Xfce is allowed to make development and stable releases at any time, see the [[http://​xfce.org/​about/​releasemodel|release model]] documentation for more information. ​   * [[http://​archive.xfce.org/​src/​xfce/​|Individual releases]]\\ Each package in Xfce is allowed to make development and stable releases at any time, see the [[http://​xfce.org/​about/​releasemodel|release model]] documentation for more information. ​
  
-===== From the code repository ​=====+==== From the code repository ====
  
 For the latest code, you need to make local copies of the [[https://​git.xfce.org/​|GIT repositories]]. This is the place where developers submit their code. If you decide to use GIT, try to use the same branch for all the packages to avoid dependency version problems. For the latest code, you need to make local copies of the [[https://​git.xfce.org/​|GIT repositories]]. This is the place where developers submit their code. If you decide to use GIT, try to use the same branch for all the packages to avoid dependency version problems.
 +
 +<note information>​For additional information about using Git with Xfce, see the [[https://​docs.xfce.org/​contribute/​dev/​git/​start|Xfce and git information]] page.</​note>​
  
 You first need to make clones of each GIT repository, like the command below, where ''​$category''​ is for example ''​xfce''​ and ''​$module''​ ''​xfce4-panel''​. If you click on a module in the [[https://​git.xfce.org/​xfce|online repository]] list, the clone uri is shown at the bottom of the page. You first need to make clones of each GIT repository, like the command below, where ''​$category''​ is for example ''​xfce''​ and ''​$module''​ ''​xfce4-panel''​. If you click on a module in the [[https://​git.xfce.org/​xfce|online repository]] list, the clone uri is shown at the bottom of the page.
Line 37: Line 45:
  
 After this, you can update your local copy of the repository with git pull and switch to another branch with ''​git checkout $branchname''​. Read the [[http://​git-scm.com/​documentation|GIT manuals]] for more information about using GIT. After this, you can update your local copy of the repository with git pull and switch to another branch with ''​git checkout $branchname''​. Read the [[http://​git-scm.com/​documentation|GIT manuals]] for more information about using GIT.
-====== Dependencies ====== 
  
-===== Build requirements ​=====+[[|Back To Top]] 
 +---- 
 +===== Xfce Dependencies explained ===== 
 + 
 +==== Build requirements ====
  
 Before you can start compiling, you need a couple of packages that are required to compile Xfce. Use your distributions package manager to install those packages. Additional packages are required too for some modules, but we'll get to that later. Before you can start compiling, you need a couple of packages that are required to compile Xfce. Use your distributions package manager to install those packages. Additional packages are required too for some modules, but we'll get to that later.
Line 57: Line 68:
  
  
-===== Xfce's dependency chain =====+==== Xfce's dependency chain ====
  
 The Xfce packages need to be built in a specific order. If you don't follow this, compile options might not be available or the configure stage will abort because of missing dependencies. The Xfce packages need to be built in a specific order. If you don't follow this, compile options might not be available or the configure stage will abort because of missing dependencies.
Line 69: Line 80:
   * xfce4-panel,​ xfce4-settings,​ xfce4-session,​ xfdesktop, xfwm4, xfce4-appfinder,​ tumbler...   * xfce4-panel,​ xfce4-settings,​ xfce4-session,​ xfdesktop, xfwm4, xfce4-appfinder,​ tumbler...
  
-===== Package specific dependencies ​=====+==== Package specific dependencies ====
  
 Some core packages in Xfce have additional or optional dependencies,​ all are listed in the table below for the latest stable version. We only show the top-dependency (so xfce4-panel also requires gtk+, but libxfce4ui already depends on that). Some core packages in Xfce have additional or optional dependencies,​ all are listed in the table below for the latest stable version. We only show the top-dependency (so xfce4-panel also requires gtk+, but libxfce4ui already depends on that).
Line 91: Line 102:
 ^ tumbler | dbus-glib, gio, gmodule, gdk-pixbuf | freetype-config (fonts), jpeg (jpeg thumbnails from exif), libffmpegthumbnailer (video), gstreamer-1.0 (video), poppler-glib (pdf), libgsf (odf), libopenraw-gnome (various raw images) | ^ tumbler | dbus-glib, gio, gmodule, gdk-pixbuf | freetype-config (fonts), jpeg (jpeg thumbnails from exif), libffmpegthumbnailer (video), gstreamer-1.0 (video), poppler-glib (pdf), libgsf (odf), libopenraw-gnome (various raw images) |
  
-====== Building ​====== +[[|Back To Top]] 
- +---- 
-===== Installation location and variables ​=====+===== Building ​the packages ​===== 
 +==== Installation location and variables ====
  
 Now it is finally time to start compiling the Xfce desktop. Last remaining thing is to choose an installation location. Possible examples are ''/​usr'',​ ''/​usr/​local''​ and ''/​opt/​xfce4''​ for a system-wide installation or ''​$HOME/​local''​ if you want to install in your home directory (whatever you choose, never put spaces in the name). We will refer to this location as ${PREFIX} in the code examples below! Now it is finally time to start compiling the Xfce desktop. Last remaining thing is to choose an installation location. Possible examples are ''/​usr'',​ ''/​usr/​local''​ and ''/​opt/​xfce4''​ for a system-wide installation or ''​$HOME/​local''​ if you want to install in your home directory (whatever you choose, never put spaces in the name). We will refer to this location as ${PREFIX} in the code examples below!
Line 108: Line 120:
  
   export CFLAGS=""​   export CFLAGS=""​
-===== Compiling and installing ​=====+   
 +==== Compiling and installing ====
  
 Next step is compiling the various packages following the dependency chain above. If you have downloaded the tarballs, you will need to unpack them before going on. Inside each package directory you should run the following command: Next step is compiling the various packages following the dependency chain above. If you have downloaded the tarballs, you will need to unpack them before going on. Inside each package directory you should run the following command:
Line 128: Line 141:
   sudo make install   sudo make install
  
-==== Debug Levels ​====+==== Understanding ​Debug levels ​====
  
 Most Xfce modules use the m4 macro //​XDT_FEATURE_DEBUG//​ to manage the debug compiler levels. If so there are a number of options possible for ''​%%--enable-debug=%%''​ Most Xfce modules use the m4 macro //​XDT_FEATURE_DEBUG//​ to manage the debug compiler levels. If so there are a number of options possible for ''​%%--enable-debug=%%''​
Line 141: Line 154:
 ! Same as the level above, including ''​-Werror''​ so the compilers aborts during compiler errors. The compiler will also generate binaries with debug information suitable for [[:​contribute:​bugs:​|backtraces]] and memory checks. This is the recommended level for developers or users who want to report bugs. ! Same as the level above, including ''​-Werror''​ so the compilers aborts during compiler errors. The compiler will also generate binaries with debug information suitable for [[:​contribute:​bugs:​|backtraces]] and memory checks. This is the recommended level for developers or users who want to report bugs.
  
-====== Help ======+[[|Back To Top]] 
 +---- 
 +===== Help =====
  
 Hopefully everything went fine after reading this guide. If you still have problems or questions you can ask on the [[http://​xfce.org/​community#​mail|Xfce users mailing list]], the [[http://​forum.xfce.org|forum]] or ask distribution related questions on their forums and mailing lists. Hopefully everything went fine after reading this guide. If you still have problems or questions you can ask on the [[http://​xfce.org/​community#​mail|Xfce users mailing list]], the [[http://​forum.xfce.org|forum]] or ask distribution related questions on their forums and mailing lists.
Line 147: Line 162:
 Have fun building Xfce! Have fun building Xfce!
  
 +[[|Back To Top]]
 +----