CVS (used for released version of MusE, 0.x-1.x NOT 2.x+)

For the newest codebase that is currently unreleased see the Svn page.

Here you find a short description on how you can get the CVS version running. If you never heard about CVS this may be a little steep. First try to download a prebuilt package for your distribution and see if that works for you.

You can also search here:
http://sourceforge.net/cvs/?group_id=93414

Contents

What you need

Development tools needed to build MusE 1.0: gnu g++ automake autoconf libtool pkgconfig

development packages for: alsa jack qt3 libsoundfile libsamplerate (optional but recommended) fluidsynth (optional but recommended) python (optional) lash (optional)

When trying to compile muse it will for most things warn that a dependency is missing so if something is missing from the list above, fetch it then and try to compile again.

Download

First get the files from cvs

cvs -z3 -d:pserver:anonymous@lmuse.cvs.sourceforge.net:/cvsroot/lmuse co -r REL07 muse
For developers (an enabled login is needed):
cvs -z3 -d:ext:<developername>@lmuse.cvs.sourceforge.net:/cvsroot/lmuse co -r REL07 -P muse

Compilation

cd muse

run the autogen script with ./autogen.sh

Do not forget to export your QTDIR variables or to pass it with the ./configure - script.

If you choose the configure script way you can see possible parameters with:

joachim@debian:~/tmp/muse-stuff/muse$ ./configure --help
 --with-docbook-stylesheets=DIR  use DIR/html/docbook.dsl
 --with-x                use the X Window System
 --with-qt-prefix=PFX    where the root of Qt is installed
 --with-qt-includes=DIR  where the Qt includes are installed
 --with-qt-libraries=DIR where the Qt libraries are installed.
 --with-qt-binaries=DIR  where the Qt binaries are installed.
 --with-qt-moc=PROG      where the Qt meta object compiler is installed.
 --with-qt-uic=PROG      where the Qt user interface compiler is installed.
 --with-alsa-prefix=PFX  prefix where alsa library is installed (optional)
 --with-alsa-inc-prefix=PFX  prefix where include libraries are (optional)

export QTDIR=/usr/share/qt3 with bash (i got debian here, so there are the qt3 libs stored)

./configure --enable-optimize --disable-debug

After all you should see something like this:

... .(here was much much more).. ...

config.status: creating lib/synthi/Makefile
config.status: creating lib/plugins/Makefile
config.status: creating plugins/Makefile
config.status: creating plugins/freeverb/Makefile
config.status: creating Doxyfile
config.status: creating config.h
config.status: executing depfiles commands
configure:
 MusE configured

 using rtcap:         no
 LASH support:      yes
 setuid root install: no
 setuid root build:   no
 fluidsynth softsynth: yes

 jade:                openjade
 doxygen:             no
 graphviz:            no
 perl:                /usr/bin/perl
 treeviews in doxygen
 html output:         no

 C++ compiler:        g++
 optimizing:          yes
 debug:               no
 optimise for arch:   none

 installation prefix: /usr/local

Hint:
If you run the "./configure ..." command from a real console and not within X the testprogram can not be run so the test fails. Do not run configure from a real console.

Hint II:
I tried to run the configure within X from a console where I used "su" to get root. In Debian you have to run "xhost +" in a x-console as normal user first to be able to run X programs as root on the same X server. This is because this increases security in some way!

./autogen problems

If you get a warning when you run "autogen.sh".

DO NOT IGNORE IT

That may be the source for many errors. If a version failed this test, update it and test again.

Running "autogen.sh"
automake version: 1.4-p6 (not ok)

####################################################################
#########################  WARNING  ################################
####################################################################

        You need automake >= 1.7!

autoconf version: 2.59 (ok)
libtool version: 1.4.3 (ok)
pkg-config: /usr/bin/pkg-config

-- In the case above you would have to update your "automake". Do this with "apt-get install automake1.7" or in case you don't have debian you might have to download the newes version of automake.


Can't build widgets A common error these days is that libtools is TOO new. this can be worked around by hand. when configure has finished (or when compilation error in 'widgets' occur) edit the file muse/widgets/Makefile Around line 312 in that file is the line: MUSECXXFLAGS the first argument there should be -c e.g. MUSECXXFLAGS = -c -g -fno-....

make command

so now the interesting part is coming:

type make

or, if you are on a multicore system you could thread make with, for instance 'make -j3' to speed up compilation

you'll see something like this:

joachim@debian:~/tmp/muse-stuff/muse$ make make all-recursive make[1]: Entering directory `/home/joachim/tmp/muse-stuff/muse' Making all in m4 make[2]: Entering directory `/home/joachim/tmp/muse-stuff/muse/m4' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/home/joachim/tmp/muse-stuff/muse/m4' Making all in synti make[2]: Entering directory `/home/joachim/tmp/muse-stuff/muse/synti' make all-recursive make[3]: Entering directory `/home/joachim/tmp/muse-stuff/muse/synti' Making all in libsynti make[4]: Entering directory `/home/joachim/tmp/muse-stuff/muse/synti/libsynti' make all-am .... (and so on)


Once you have made a fix

You can use CVS to generate a patch like so:

foo@bar:~/Repository/muse/ cvs diff -u synti/vam/vamguibase.ui
Index: synti/vam/vamguibase.ui
===================================================================
RCS file: /cvsroot/lmuse/muse/synti/vam/vamguibase.ui,v
retrieving revision 1.4
diff -u -r1.4 vamguibase.ui
--- synti/vam/vamguibase.ui 13 Feb 2004 21:35:22 -0000 1.4
+++ synti/vam/vamguibase.ui 31 Mar 2004 22:31:56 -0000
@@ -1,4 +1,4 @@
-<!DOCTYPE UI><UI version="3.3" stdsetdef="1"> +<!DOCTYPE UI><UI version="3.2" stdsetdef="1">

<class>VAMGuiBase</class>
<widget class="QWidget">
    <property name="name">

Please submit patches to lmuse-devel@sourceforge.net for evaluation and inclusion.
You can paste the text into your email, or redirect stdout to an appropriately named file for attachment.

---

Completed

When compilation is finished try installing it with 'sudo make install'. After you installed the software type 'muse' in console. Do not forget to start jackd as the same user as you run MusE. I assume you run as root so open a second terminal and type "jackd -d alsa". If your done with testing as root I recommand to run MusE as a normal but with special execution rights (sudo?)

If you got an older version of muse installed, remove it. This is done with apt-get remove muse. Or in similar steps with the tool "rpm".

Powered by MediaWiki