Rosegarden – music editor and MIDI/audio sequencer
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.


  1. How to compile Rosegarden
  2. =========================
  3. Rosegarden has switched its build system to CMake. We hope this will
  4. be the last time we change build systems.
  5. You will need CMake 2.4.2 or later. If your Linux distribution
  6. doesn't provide CMake, or if it provides an older version, you can get
  7. it here:
  9. There are ready to use binary packages available for Linux-i386 from
  10. that page. They seem to work well -- use them! We advise you avoid
  11. building CMake from source if possible. (If you must build it from
  12. source, please read the instructions supplied with the CMake tarball,
  13. and remember that it will install to /usr/local by default.)
  14. A Typical Build with CMake
  15. ---------------------------
  16. If you are a typical end user wanting to play with the latest
  17. Rosegarden, and to install it in the same place the distro package you
  18. are replacing came from, then the the following instructions are
  19. probably all you need to do in order to get up and running:
  20. First, unpack the tarball or check out SVN. We'll assume you have the
  21. source in ~/src/rosegarden and need to change to that directory:
  22. $ cd ~/src/rosegarden
  23. Now run CMake to generate the build files, and specify the location
  24. where your system's KDE libraries are installed. A nice general way
  25. to do this is:
  26. $ cmake . -DCMAKE_INSTALL_PREFIX=`tde-config --prefix`
  27. If you omit the install prefix and just run
  28. $ cmake .
  29. instead, cmake will prepare to install Rosegarden and its data files
  30. beneath /usr/local. That may be fine if you have no existing
  31. Rosegarden installation you want to replace (see also Advanced Build
  32. Options below).
  33. Finally, run make, and then (sudo) make install, and you're all set:
  34. $ make
  35. # make install
  36. To uninstall, use:
  37. # make uninstall
  38. Advanced Build Options
  39. ----------------------
  40. By default, make will output brief details of each build step. If you
  41. prefer to see full command lines, use:
  42. $ make VERBOSE=1
  43. By default, the install prefix will be /usr/local. If your KDE is
  44. installed at some other prefix, you probably want to override this
  45. setting, as suggested in "A Typical Build with CMake." You may
  46. install to /usr/local or anywhere else, but if you do so, you must add
  47. that location to your TDEDIRS environment variable before running
  48. Rosegarden. For example:
  49. $ export TDEDIRS=/usr/local:$TDEDIRS
  50. $ rosegarden
  51. Another option, useful for packagers, is setting DESTDIR at install
  52. time. The DESTDIR directory will be prepended to the prefix when
  53. copying the files:
  54. $ make install DESTDIR=~/rpmroot
  55. Some variables you may want to set:
  57. cmake . -DCMAKE_INSTALL_PREFIX=/opt/kde is the equivalent to
  58. ./configure --prefix=/opt/kde for programs that use autotools
  59. * WANT_XXXX: there are several options, e.g. WANT_JACK or WANT_DSSI.
  60. If you disable them, cmake will not even try to find the packages.
  61. WANT_DEBUG Include debug support (default OFF)
  62. WANT_FULLDBG Full debug support (BIG executables!) (default OFF)
  63. WANT_SOUND Include MIDI support using ALSA (default ON)
  64. WANT_JACK Include audio support using JACK (default ON)
  65. WANT_DSSI Include DSSI plugin support (default ON)
  66. WANT_LIRC Include LIRC (Linux Infrared Remote Control) support (def. ON)
  67. WANT_PCH Use precompiled headers (default OFF)
  68. The above options can take any of the following values: 0, 1, OFF, ON,
  69. TRUE, FALSE, YES, NO (case insensitive). For example:
  71. Disabling SOUND (eg. WANT_SOUND=OFF) also disables JACK and DSSI. To
  72. enable FULLDBG you also need to enable DEBUG.
  73. If you would prefer to avoid all this typing, you can use ccmake to
  74. view and change these options using a friendly curses-based interface:
  75. $ ccmake .
  76. Dealing with Configuration Problems
  77. -----------------------------------
  78. To locate Qt, CMake searches for qmake in your execute path
  79. ($PATH). CMake does not use the TQTDIR environment variable. So make
  80. sure that the first qmake found in the execution path is the one you
  81. like to use.
  82. When CMake has finished, it will have created a file called
  83. "CMakeCache.txt". This file contains all the settings CMake has
  84. detected on your system. If you want to run CMake with another
  85. generator or you want CMake to detect everything again, delete this
  86. file.
  87. If CMake didn't find something, but you know it is somewhere on your
  88. box, you can tell CMake where to find it manually. CMake uses
  89. variables to store this information. These variables are cached in the
  90. aforementioned file CMakeCache.txt. You have three options to adjust
  91. these variables manually:
  92. * tell CMake the correct value via the command line:
  93. $ cmake . -DNAME_OF_THE_VARIABLE=value
  94. * use ccmake, which provides a curses based GUI to adjust the
  95. CMake variables (run: ccmake .)
  96. * edit the file CMakeCache.txt directly (not recommended)
  97. You should run "ccmake ." at least once so that you get an idea which
  98. variables CMake uses. Press "T" to see also the "advanced"
  99. variables. So, if CMake didn't find something, start ccmake and adjust
  100. it manually.
  101. Some other environment variables you may want to set
  102. ----------------------------------------------------
  103. If you have headers and libraries installed in non-standard locations
  104. that cmake cannot find (e.g., on /sw), then set the following as
  105. environment variables. Despite the similar naming convention, these
  106. will not work as arguments on the cmake command line:
  107. * CMAKE_INCLUDE_PATH: directory where headers reside
  108. * CMAKE_LIBRARY_PATH: directory where shared libraries reside
  109. Example:
  110. $ export CMAKE_INCLUDE_PATH=/sw/include
  111. $ export CMAKE_LIBRARY_PATH=/sw/lib
  112. For more information on variables, see this wiki page:
  114. How to proceed if something fails?
  115. ----------------------------------
  116. If cmake finishes with "Generating done" then there was no errors, but
  117. if it finishes with "Configuring done" then there was errors that you
  118. have to fix. If you got a failure that says something like
  119. CMake Error: This project requires some variables to be set,
  120. and cmake can not find them.
  121. Please set the following variables:
  122. X11_XTest_LIB (ADVANCED)
  123. So the missing library is Xtst. Perhaps you need to install a
  124. libXtst-devel library.
  125. If you can't solve the problem, please subscribe and ask your question
  126. on the rosegarden-user mailing list: