Differences

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

Link to this comparison view

Next revision
Previous revision
installingfromsource [2013/06/01 01:44]
sanel created
installingfromsource [2013/06/11 13:51]
sanel Fixed old moinmoin bugzilla tag to be recognized by doku
Line 2: Line 2:
  
 ===== Prerequisites ===== ===== Prerequisites =====
-Make sure you have listed requirements or EDE will not compile. If required ​packages has given version, please use that (or greater) release.+Make sure you have listed requirements or ''​EDE''​ might not compile ​(properly). If required version ​was mentioned, please use that (or a newer) release.
  
 ==== Required programs and libraries ==== ==== Required programs and libraries ====
-This is the list of must-have programs and libraries or EDE and edelib (EDE Library) compilation will fail. All these programs and libraries ​already should came with your distribution as package (or as opt-in from package repository) and if they are not installed, please ​use your distribution specific installation procedure ​to install it+This is the list of must-have programs and libraries or ''​EDE'' ​and ''​edelib'' ​(''​EDE'' ​Library) compilation will fail. All these programs and libraries are usually already part of a default installation on most distributions. If not, they can most likely be installed ​via your distributions repositories. If all else failsyou can compile them from source, too (in that case please ​refer to the documentation of that packages for more information on how to do that)
-  * C++ compiler (g++ >= 2.95 or newer or any recent ​!SunStudio ​version). Compiling ​on clang or intel c++ wasn't tested, but should be possible +  * C++ compiler (g++ >= 2.95 or newer, Clang or any recent ​%%SunStudio%% versions). Compiling ​with Intel C++ wasn't tested, but should be possible 
-  * pkg-config+  * [[http://​www.freedesktop.org/​wiki/​Software/​pkg-config/​|pkg-config]] or [[https://​github.com/​pkgconf/​pkgconf|pkgconf]]
   * [[http://​www.fltk.org|FLTK]] >= 1.1.7   * [[http://​www.fltk.org|FLTK]] >= 1.1.7
   * [[http://​www.freedesktop.org/​wiki/​Software/​dbus|DBus]] >= 1.0   * [[http://​www.freedesktop.org/​wiki/​Software/​dbus|DBus]] >= 1.0
-  * autoconf and aclocal (aclocal is part of automake package) are needed //only// if you downloaded EDE sources directly from the repository+  * autoconf and aclocal (aclocal is part of automake package) are needed //only// if you downloaded ​''​EDE'' ​sources directly from the source ​repository
  
 ==== Optional programs and libraries ==== ==== Optional programs and libraries ====
-This is the list of programs and libraries used by EDE and edelib we would like you have, but are not mandatory. If they are not present, certain features ​could be disabled.+This is the list of programs and libraries used by ''​EDE'' ​and ''​edelib'' ​we would like you to have, but which are not mandatory. If they are not present, certain features ​might be disabled.
  
-=== edelib ​=== +=== Edelib ​=== 
-  * doxygen - used to make API documentation+  * doxygen - used to create ​API documentation
   * inotify (present in linux kernel since 2.6.13) or Gamin/Fam   * inotify (present in linux kernel since 2.6.13) or Gamin/Fam
  
 === EDE === === EDE ===
-  * python >= 2.3 - used to make documentation +  * python >= 2.3 - used to create ​documentation 
-  * UPower - comes with newer distributions (you can find more at http://​upower.freedesktop.org) +  * UPower - comes with newer distributions (you can find out more at http://​upower.freedesktop.org) 
-  * librsvg (only used rsvg tool) - used to create //edeneu// theme from .svg icons; this is only needed if you downloaded EDE directly from the repository +  * librsvg (only used rsvg tool) - used to create ​the //edeneu// theme from .svg icons; this is only needed if you downloaded ​''​EDE'' ​directly from the source ​repository 
-  * xscreensaver - should come with your distribution +  * xscreensaver - usually comes with your distribution 
-  * [[http://​curl.haxx.se/​|cURL]] - used for bug report tool; it should come with your distribution ​+  * [[http://​curl.haxx.se/​|cURL]] - used for the [[ede-bug-report|bug reporting ​tool]]; it should come with your distribution ​
  
-There is known issue <<​Bugzilla(156)>> ​with python >= 2.6.2 and building EDE documentation. If you get into the problems as described in bug report, please use the solution given in the comment ​of that report.+There is known issue (Bug 156) with python >= 2.6.2 and building EDE documentation. If you get into the problems as described in the bug report, please use the solution given in the comment ​on that report.
  
 ==== EDE programs and libraries ==== ==== EDE programs and libraries ====
-This is the list of EDE related programs and libraries you should download from our download pages:+This is the list of ''​EDE'' ​related programs and libraries you should download from our download pages:
   * jam   * jam
   * edelib 2.0   * edelib 2.0
Line 37: Line 37:
  
 ===== Compiling EDE ===== ===== Compiling EDE =====
-After you extracted each of EDE related programs, compile them in given order below.+After you extracted each of ''​EDE'' ​related programs, compile them in the order given below.
  
-=== Compile ​jam === +=== Compiling ​jam === 
-Jam is make replacement we are using to compile EDE and edelib. Some distributions ​provides jam package ​so make sure it is official ​jam or ftjam; common version tody is //​Boost ​jam// too, but EDE can't be compiled ​with it!+''​JAM''​ ("//​Just Another Make//"​) ​is make replacement we are using to compile ​''​EDE'' ​and ''​edelib''​. Some distributions ​provide a ''​JAM'' ​package. **__Make ​sure it is the official ​''​JAM'' ​or ''​FTJAM''​__**another ​common version tody is //​Boost ​JAM//, but ''​EDE'' ​can't be built with it!
  
-To see if it official jam, execute:+To see if it is the official jam, execute:
  
 <​code>​ <​code>​
Line 60: Line 60:
 </​code>​ </​code>​
  
-then is ok. If you are not sure what jam version you have (but have already ​some), let edelib'​s configure script ​detects ​it and report if can be used. You can always download ​jam we are using from our download pages is you are not sure.+then it is ok. If you are not sure what jam version you have (but already ​one installed), let ''​edelib''​'s configure script ​detect ​it and report if it can be used. You can always download ​the ''​JAM''​ version ​we are using from our download pages if you are not sure.
  
-If you downloaded ​jam sourceit already comes with Makefile, so running:+Once you downloaded ​the ''​JAM'' ​source ​decompress ​it. It already comes with Makefile, so simply ​running:
  
 <​code>​ <​code>​
Line 70: Line 70:
 will compile it. will compile it.
  
-Installation is done by copying ​jam binary ​at the common binary location, like ///​usr/​local/​bin//​. ​Jam binary will be compiled in //​bin.YOUROS//​ location, where YOUROS is operating system you are running, e.g. on Linux, ​jam will be in //​bin.linuxx86//​ and on FreeBSD will be in //​bin.freebsdx86//​. If you are using ftjam, binary directory will be //​bin.unix//​.+Installation is done by copying ​''​JAM''​s' ​binary ​to a common binary location, like ///​usr/​local/​bin//​. ​The binary will be compiled in //​bin.YOUROS//​ location, where YOUROS is operating system you are running, e.g. on Linux, ​the executable ​will be in //​bin.linuxx86//​ and on FreeBSD will be in //​bin.freebsdx86//​. If you are using ''​FTJAM''​the binary directory will be //​bin.unix//​.
  
 Copying is done with: Copying is done with:
Line 79: Line 79:
  
 === Compiling edelib === === Compiling edelib ===
-In case you downloaded edelib from repository, make sure to run:+In case you downloaded ​''​edelib'' ​from the source ​repository, make sure to run:
  
 <​code>​ <​code>​
Line 85: Line 85:
 </​code>​ </​code>​
  
-first and it will create correct configure script. If you downloaded official source release, this step is not needed because configure script ​is already created. The rest is:+first as that will create ​the correct configure script. If you downloaded ​the official source release, this step is not needed because ​configure script ​was already created. The rest is executing:
  
 <​code>​ <​code>​
Line 91: Line 91:
 </​code>​ </​code>​
  
-and run jam (not make!):+then running ​jam (not make!):
  
 <​code>​ <​code>​
Line 97: Line 97:
 </​code>​ </​code>​
  
-and as superuser:+and finally ​as superuser:
  
 <​code>​ <​code>​
Line 104: Line 104:
  
 === Compiling ede === === Compiling ede ===
-If you installed edelib with different prefix than ///usr//, export that path to pkg-config so it can find edelib libraries. To do so, run:+If you installed ​''​edelib'' ​with different prefix than ///usr//, export that path to pkg-config so it can find the ''​edelib'' ​libraries. To do so, run:
 <​code>​ <​code>​
 export PKG_CONFIG_PATH=<​your-prefix>/​lib/​pkgconfig export PKG_CONFIG_PATH=<​your-prefix>/​lib/​pkgconfig
 </​code>​ </​code>​
  
-Compiling ​ede is the same as for edelib. Also, if you downloaded ​ede sources from repository, make sure to run:+Compiling ​''​EDE'' ​is the same as for ''​edelib''​. Also, if you downloaded ​''​EDE'' ​sources from source ​repository, make sure to run:
 <​code>​ <​code>​
 ./​autogen.sh ./​autogen.sh
Line 120: Line 120:
 </​code>​ </​code>​
  
-then:+afterwards:
  
 <​code>​ <​code>​
Line 126: Line 126:
 </​code>​ </​code>​
  
-and as superuser:+and finally ​as superuser:
  
 <​code>​ <​code>​
Line 132: Line 132:
 </​code>​ </​code>​
  
-:!: Note: if you downloaded ​ede source code from repository (//ede2// module) default icon theme is not built, so you must do it manually. This is really simple procedure where you should pass only one parameter to jam tool (you have to have librsvg installed too). So, instead //jam// and //jam install// as given above, you should run:+:!: **Note:** if you downloaded ​''​EDE'' ​source code from repository (//ede2// module) ​the default icon theme is not built, so you must do it manually. This is really simple procedure where you should pass only one parameter to the ''​JAM'' ​tool (you have to have librsvg installedtoo). So, instead ​of just //jam// and //jam install// as given above, you should run:
  
 <​code>​ <​code>​
Line 144: Line 144:
 </​code>​ </​code>​
  
-This will build ede and icon theme, installing both.+This will build ''​EDE'' ​and icon theme, installing both.
  
 ===== Starting EDE ===== ===== Starting EDE =====
-If you are using display or login manager (like gdm, kdm or xdm) and you installed EDE with default prefix (it will use ///usr// by default), you will see session entry named **EDE** in display manager'​s list of available sessions. However, if you install EDE with different prefix, make sure to copy **ede.desktop** file (you will find it at //<​prefix>/​share/​xsessions/​ede.desktop//​ path) to ///​usr/​share/​xsessions//​ folder, or configure your display manager to see EDE installation path.+If you are using display or login manager (like gdm, kdm or xdm) and you installed ​''​EDE'' ​with default prefix (it will use ///usr// by default), you will see session entry named **EDE** in your display manager'​s list of available sessions. However, if you install ​''​EDE'' ​with different prefix, make sure to copy the //ede.desktop// file (you will find it at //<​prefix>/​share/​xsessions/​ede.desktop//​ path) to ///​usr/​share/​xsessions//​ folder, or configure your display manager to find ''​EDE'''​s ​installation path.
  
-If you are not using display manager (you start X session from terminal with //startx// command), put **startede** at the end of //​.xinitrc//​ file (found in your home directory, like ///​home/​your_username/​.xinitrc//,​ but make sure you comment previous window managers or desktop starting scripts if they exists.+If you are not using display manager (you start X session from terminal with //startx// command), put **startede** at the end of the //​.xinitrc//​ file (found in your home directory, like ///​home/​your_username/​.xinitrc//,​ but make sure you comment previous window managers or desktop starting scripts if they exist.
  
 If you do not have //​.xinitrc//​ file in your home directory or you are not sure how things should be modified, here is a working sample you can copy and paste: If you do not have //​.xinitrc//​ file in your home directory or you are not sure how things should be modified, here is a working sample you can copy and paste:
Line 187: Line 187:
  
 ===== Conclusion ===== ===== Conclusion =====
-That would be it. Happy using and let us know what you are thinking about itPlease report any issues ​at http://​bugs.equinox-project.org. +That would be it. Happy using and let us know what you are thinking about itPlease report any issues ​you might encounter on http://​bugs.equinox-project.org.
Print/export