Hi Charles! On Mon, Aug 19, 2002 at 01:23:56PM -0400, Charles A Edwards wrote: > On Mon, 19 Aug 2002 15:17:33 +0200 > Goetz Waschk <[EMAIL PROTECTED]> wrote: > > > I just tried to build it, the configure script failed at the arts > > test. Does anyone want to fix this? > > I can tell you how to fix it but I do not know if it should be written > as a patch or done in some other manner, so I will leave that to you. > > Line# 9027 in configure needs to be changed from: > CPPFLAGS="$CPPFLAGS -I$kde_includes" > > To: > CPPFLAGS="$CPPFLAGS -I$/usr/includes"
This works for me, too but I don't quite understand this hack ;)
(/usr/include is the include dir, there is a $ in front of the
-I, does that mean there is a $/usr/includes variable ??)
> Make will complete with the above change made.
That should be configure ;)
> Modifying accordingly the current brahms.spec rpm build fails at :
>
> ...
This works, if you apply the SuSe gcc-3.1 patch and the gcc.dif
patches, the first one merged with Mandrake's one which I like better :)
Also I included my brahms.spec file, but it doesn't work without
an additional awk/sed line for configure or a patch for configure.in
or whatever. Because of mail space problems I send the big patch in
a separate mail.
SuSE spec file contained a script I did not find on my Beta2 system:
/ect/opt/kde3/common_options
./configure $configkde --disable-final
With best regards,
Reinhard Katzmann
brahms.spec:
%define name brahms
%define version 1.02
%define release 4mdk
%define kdever kde3
%define major 0
Summary: Music sequencer and notation program
Name: %{name}
Version: %{version}
Release: %{release}
Source0: %{name}-%{version}-%{kdever}.tar.bz2
Source1: %{name}-16.png.bz2
Source2: %{name}-32.png.bz2
Source3: %{name}-48.png.bz2
#Patch0: %{name}-patch.bz2
Patch1: %{name}.dif
Patch2: %{name}-gcc3.1.patch
URL: http://brahms.sourceforge.net/
License: GPL
Group: Sound
BuildRoot: %{_tmppath}/%{name}-buildroot
Prefix: %{_prefix}
Requires: lib%{name} = %{version}-%{release}
BuildRequires: libarts2-devel
BuildRequires: kdelibs
BuildRequires: kdemultimedia-devel
Buildrequires: libfam0-devel
Buildrequires: libaudiofile0-devel
BuildRequires: libalsa2-devel
BuildRequires: XFree86-devel
BuildRequires: libjpeg-devel
Buildrequires: libqt3-devel
Buildrequires: kdelibs-devel
Buildrequires: libpng-devel
%description
The Brahms software provides an environment to operate
on music data. At first, a piece of music is coded as a
collection of midi events kept in parts and tracks
- the structures of a Brahms song.
Especially note objects keep extended information
for intonation and abstract properties (like enharmonic
shift), which the midi format lacks. These notes can of
course be played with Brahms via the midi interface.
%package -n lib%{name}%{major}
Summary: Libraries need by %{name}
Group: System/Libraries
Provides: lib%{name}
Requires: %{name} = %{version}-%{release}
%description -n lib%{name}%{major}
Libraries need to run brahms
%prep
%setup -n Brahms
#%%patch -p1
%patch1 -p 0 -E
%patch2 -p1
%build
./configure --disable-rpath --disable-final --prefix=%{_prefix}
%make
%install
rm -rf $RPM_BUILD_ROOT
# Laurent %%makeinstall doesn't work
make install DESTDIR=$RPM_BUILD_ROOT/
bzcat %{SOURCE1} > %{name}-16.png
bzcat %{SOURCE2} > %{name}-32.png
bzcat %{SOURCE3} > %{name}-48.png
install -D -m 644 %{name}-16.png $RPM_BUILD_ROOT%{_miconsdir}/%{name}.png
install -D -m 644 %{name}-32.png $RPM_BUILD_ROOT%{_iconsdir}/%{name}.png
install -D -m 644 %{name}-48.png $RPM_BUILD_ROOT%{_liconsdir}/%{name}.png
(cd $RPM_BUILD_ROOT
mkdir -p ./%{_menudir}
cat > ./%{_menudir}/brahms <<EOF
?package(%{name}):\
command="%{_bindir}/brahms"\
title="Brahms"\
longtitle="Music sequencer"\
needs="x11"\
icon="%{name}.png"\
section="Multimedia/Sound"
EOF
)
%post
%{update_menus}
%postun
%{clean_menus}
%post -n lib%{name}%{major} -p /sbin/ldconfig
%postun -n lib%{name}%{major} -p /sbin/ldconfig
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root)
%_bindir/%name
%_datadir/doc/*
%_datadir/icons/*
%dir %_datadir/apps/%name/
%_datadir/apps/%name/*.rc
%dir %_datadir/apps/%name/pics/
%_datadir/apps/%name/pics/*
%_menudir/*
# icons
# %{_iconsdir}/%{name}.png
# %{_miconsdir}/%{name}.png
# %{_liconsdir}/%{name}.png
%doc README.brahms doc/arts-linuxtag2001.ps
%files -n lib%{name}%{major}
%defattr(-,root,root)
%{_libdir}/*.so
%{_libdir}/*.so.*
%{_libdir}/*.la
%{_libdir}/mcop/*
%changelog
* Mon Aug 19 2002 Reinhard Katzmann <[EMAIL PROTECTED]> 1.02 -4mdk
- Fix spec file to use kde3 archive, compiled with gcc3.2
- Add more patches to get arts problems fixed.
- Comment original mdk patch (merged with gcc-3.1 patch)
- TODO: configure, line 2097 should be -I$/usr/includes, but
I don't know how to make a good fix for this
brahms.dif:
--- brahms/arts/BrahmsMidiRecorder.cpp
+++ brahms/arts/BrahmsMidiRecorder.cpp 2002/06/12 12:23:15
@@ -73,6 +73,4 @@
};
-REGISTER_IMPLEMENTATION(BrahmsMidiRecorder_impl);
-
#endif
--- brahms/main.cpp
+++ brahms/main.cpp 2002/06/12 12:23:15
@@ -53,7 +53,7 @@
char * presentation = parameter("--presentation", "-p",argc,argv);
char * out = parameter("--output", "-o",argc,argv);
- output = 1;
+ output = ALSA;
if (out>0) {
if (strcmp(out,"kmid")==0) output = KMID;
if (strcmp(out,"arts")==0) output = ARTS;
--- doc/brahms/index.docbook
+++ doc/brahms/index.docbook 2002/06/12 12:46:47
@@ -85,17 +85,19 @@
<sect1 id="developers">
<title>The Brahms API - For Developers</title>
<para>
-To develop further functionality via the Brahms addon mechanism, read
+To develop further functionality via the Brahms addon mechanism, read:</para>
<itemizedlist>
-<listitem>the section about <link linkend="addons">Addons</link>.</listitem>
-<listitem>the <ulink url="api/html/hier.html">api documentation</ulink> contains the
basic classes which can be used when programming addons.</listitem>
-<listitem>As one example the <ulink url="api/html/Dump.html">Dump</ulink> addon (see
<ulink url="api/html/dump_h.html">dump.h</ulink> and
-<ulink url="api/dump.cpp">dump.cpp</ulink>) may be examined and modified!</listitem>
+<listitem><para>the section about <link
+linkend="addons">Addons</link>.</para></listitem>
+<listitem><para>the <ulink url="api/html/hier.html">api documentation</ulink>
+contains the basic classes which can be used when programming
+addons.</para></listitem>
+<listitem><para>As one example the <ulink url="api/html/Dump.html">Dump</ulink> addon
+(see <ulink url="api/html/dump_h.html">dump.h</ulink> and
+<ulink url="api/dump.cpp">dump.cpp</ulink>) may be examined and
+modified!</para></listitem>
</itemizedlist>
-</para>
+
</sect1>
<sect1>
+<title>The &brahms; Interface</title>
<para>
<screenshot>
<mediaobject>
@@ -184,9 +186,9 @@
A &brahms; song consists of several tracks. Different tracks can be used to contain
different voices of a piece of music. Among the
tracks properties are:
<itemizedlist>
-<listitem>a mute switch</listitem>
-<listitem>the track type (see below)</listitem>
-<listitem>the name</listitem>
+<listitem><para>a mute switch</para></listitem>
+<listitem><para>the track type (see below)</para></listitem>
+<listitem><para>the name</para></listitem>
</itemizedlist>
</para>
@@ -194,15 +196,15 @@
<title>Tracks</title>
<para>
-A track may be of one of the following types:
+A track may be of one of the following types:</para>
<itemizedlist>
-<listitem>ScoreTrack - used for score editing</listitem>
-<listitem>DrumTrack - used for drum editing, the contained information does not
differ from the ScoreTrack</listitem>
-<listitem>MasterTrack - used to regulate changes in tempo and meter</listitem>
-<listitem>AudioTrack - will be used soon for harddisc recording and playback of
wave-files</listitem>
-<listitem>CommentTrack - used to store textual information with the song</listitem>
+<listitem><para>ScoreTrack - used for score editing</para></listitem>
+<listitem><para>DrumTrack - used for drum editing, the contained information does not
+differ from the ScoreTrack</para></listitem>
+<listitem><para>MasterTrack - used to regulate changes in tempo and
+meter</para></listitem>
+<listitem><para>AudioTrack - will be used soon for harddisc recording and playback of
+wave-files</para></listitem>
+<listitem><para>CommentTrack - used to store textual information with the
+song</para></listitem>
</itemizedlist>
-For the future there will be a general track type, which can be used to implement
other track types within an addon (like a video track).
+<para>For the future there will be a general track type, which can be used to
+implement other track types within an addon (like a video track).
</para>
<para>
<screenshot>
@@ -218,16 +220,16 @@
</para>
<para>
-For Scoretracks and Drumtracks, there are more properties like:
+For Scoretracks and Drumtracks, there are more properties like:</para>
<itemizedlist>
-<listitem>the midi instrument</listitem>
-<listitem>the output device</listitem>
-<listitem>the midi channel (by default the notes' channel is used)</listitem>
-<listitem>a relative volume parameter</listitem>
-<listitem>a relative pitch parameter (transposition)</listitem>
-<listitem>a relative delay parameter</listitem>
+<listitem><para>the midi instrument</para></listitem>
+<listitem><para>the output device</para></listitem>
+<listitem><para>the midi channel (by default the notes' channel is
+used)</para></listitem>
+<listitem><para>a relative volume parameter</para></listitem>
+<listitem><para>a relative pitch parameter (transposition)</para></listitem>
+<listitem><para>a relative delay parameter</para></listitem>
</itemizedlist>
-The relative parameters are added to the events during playback. A chosen midi
channel overrules the notes' channel property, but
+<para>The relative parameters are added to the events during playback. A chosen midi
+channel overrules the notes' channel property, but
does not change it.
</para>
</sect2>
@@ -246,11 +248,11 @@
All events have a position in time, relative to the start position of the part, as
well as a duration in time. There are
several event types:
<itemizedlist>
-<listitem>MidiEvent - these are all midi events, except for note-on and
note-off</listitem>
-<listitem>MasterEvent - containing information about tempo and meter</listitem>
-<listitem>Note - the combined data of a midi note-on and note-off event, and some
additional information (see below)</listitem>
-<listitem>AudioEvent - these contain a filename pointing to a wave file</listitem>
-<listitem>Symbol - containing special symbols for ScoreEditing</listitem>
+<listitem><para>MidiEvent - these are all midi events, except for note-on and
+note-off</para></listitem>
+<listitem><para>MasterEvent - containing information about tempo and
+meter</para></listitem>
+<listitem><para>Note - the combined data of a midi note-on and note-off event, and
+some additional information (see below)</para></listitem>
+<listitem><para>AudioEvent - these contain a filename pointing to a wave
+file</para></listitem>
+<listitem><para>Symbol - containing special symbols for ScoreEditing</para></listitem>
</itemizedlist>
</para>
</sect2>
@@ -279,15 +281,15 @@
</para>
<para>
-Addons can be used in differend scopes, listed here ordered from small to large:
+Addons can be used in differend scopes, listed here ordered from small to
+large:</para>
<itemizedlist>
-<listitem>selection</listitem>
-<listitem>part</listitem>
-<listitem>track</listitem>
-<listitem>song</listitem>
-<listitem>global</listitem>
+<listitem><para>selection</para></listitem>
+<listitem><para>part</para></listitem>
+<listitem><para>track</para></listitem>
+<listitem><para>song</para></listitem>
+<listitem><para>global</para></listitem>
</itemizedlist>
-When writing an addon, the scope in which the new addon shall be able to operate has
to be specified. Of course
+<para>When writing an addon, the scope in which the new addon shall be able to
+operate has to be specified. Of course
multiple scope are possible. The "global" scope allows to provide functionality which
does not operate on a
song or any part of it. An example for this is the "EarTraining" addon.
</para>
@@ -426,16 +428,13 @@
<textobject>
<phrase>The EarTraining Addon</phrase>
</textobject>
- <caption>The EarTraining Addon</caption>
- </mediaobject>
+<caption><para>The EarTraining Addon</para></caption>
+ </mediaobject>
</screenshot>
</para>
-</sect1>
-
<para>
-
For editing music, &brahms; provides different editors. There is the score
editor, where notes are displayed and can be modified as musicians would do
on note paper or in a score. On the other hand, there is a piano roll editor.
@@ -444,7 +443,7 @@
</para>
-
+</sect1>
</chapter>
@@ -471,23 +470,22 @@
Brahms [options]* [filename]
</para>
<para>
-where options are:
+where options are:</para>
<itemizedlist>
-<listitem> -a, --addon <MODULENAME>: Loads the specified module (e.g. dump,
parallels, stretch, ...)</listitem>
-<listitem> -h, --help: Displays this message</listitem>
-<listitem> -o, --output <OUTPUT>, where <OUTPUT> is one of "arts"
(default) or "alsa" (only works with alsa 0.5.x)</listitem>
-<listitem> -p, --presentation <LIB>, where <LIB> is one of "text",
"kde" (default), or the libraryname</listitem>
-<listitem> -v, --version: Displays the version number</listitem>
+<listitem><para>-a, --addon MODULENAME: Loads the specified module (e.g. dump,
+parallels, stretch, ...)</para></listitem>
+<listitem><para>-h, --help: Displays this message</para></listitem>
+<listitem><para> -o, --output <OUTPUT>, where <OUTPUT> is one of "arts"
+(default) or "alsa" (only works with alsa 0.5.x)</para></listitem>
+<listitem><para> -p, --presentation <LIB>, where <LIB> is one of
+"text", "kde" (default), or the libraryname</para></listitem>
+<listitem><para> -v, --version: Displays the version
+number</para></listitem>
</itemizedlist>
-</para>
</sect1>
<sect1 id="main-window">
<title>The Main Window</title>
<para>
The main window consists mainly of two areas, offering a view on the tracks on the
left
-and a view on the parts to the right, headed by a timescale.
-<para>
+and a view on the parts to the right, headed by a timescale.</para>
+
<screenshot>
<mediaobject>
<imageobject>
@@ -498,7 +496,8 @@
</textobject>
</mediaobject>
</screenshot>
-</para>
+
+<para>
With an empty song, there exist no tracks or parts at startup. Tracks and parts can
be added either
via the menu "add->track" and the contextmenu "add part" which pops up after clicking
the right mouse
button on the track name - or just by
@@ -530,6 +529,7 @@
<title>All Editors Keyboard Shortcuts</title>
<para>
<table>
+<title>All Editors Keyboard Shortcuts</title>
<tgroup cols="2">
<thead>
<row>
@@ -567,17 +567,18 @@
</para>
</sect2>
-<para>
-General rules for mouse actions:
+<sect2>
+<title>General rules for mouse actions</title>
+
<itemizedlist>
-<listitem> Pressing the left mouse button somewhere inside the canvas inserts a note
at that pitch and position. </listitem>
-<listitem> Pressing the left mouse button inside the canvas and releasing it
somewhere else selects the notes inside the specified area. </listitem>
-<listitem> Moving the mouse over a note changes the mouse cursor. </listitem>
-<listitem> Pressing the left mouse button on a note selects that note. </listitem>
-<listitem> Pressing the left mouse button on a note and moving the mouse moves that
note (or selection) to the pitch and position the mouse button is released. </listitem>
-<listitem> Different editors have different context menus, when the right mouse
button is pressed over a note. </listitem>
+<listitem><para>Pressing the left mouse button somewhere inside the canvas inserts a
+note at that pitch and position.</para></listitem>
+<listitem><para>Pressing the left mouse button inside the canvas and releasing it
+somewhere else selects the notes inside the specified area.</para></listitem>
+<listitem><para>Moving the mouse over a note changes the mouse
+cursor.</para></listitem>
+<listitem><para>Pressing the left mouse button on a note selects that note.</para>
+</listitem>
+<listitem><para>Pressing the left mouse button on a note and moving the mouse moves
+that note (or selection) to the pitch and position the mouse button is
+released.</para> </listitem>
+<listitem><para>Different editors have different context menus, when the right mouse
+button is pressed over a note. </para></listitem>
</itemizedlist>
-</para>
+
<para>
The bottom area of most editors shows the velocity (volume) values of the notes
displayed above. Use the mouse to change a sinlge velocity value, or simply drag the
@@ -587,7 +588,7 @@
<para>
For developers: All editors are based on an abstract editor class (PrPartEditor),
which makes it easy to implement new Editors of any kind.
</para>
-
+</sect2>
</sect1>
<!-- -->
@@ -611,17 +612,14 @@
</screenshot>
</para>
-<para>
-
-</para>
-
-<sect2 id="editorshortcuts">
+<sect2 id="editor-shortcuts-additional">
<title>The Score Editors Additional Keyboard Shortcuts</title>
<para>
The Shortcuts to be used within the score editor are those described in section <link
linkend="editorshortcuts">Editor Shortcuts</link>, plus the following additional
shortcuts.
</para>
<para>
<table>
+<title>The Score Editors Additional Keyboard Shortcuts</title>
<tgroup cols="2">
<thead>
<row>
@@ -643,11 +641,13 @@
To insert lyrics, press the left mouse button when over the note: Enter the lyrics
into the text field - the RETURN key closes the text field, while the
SPACE key moves it to the next syllable.
</para>
-</sect2>
+
+
+
<para>
For developers: Even the ScoreEditor is based on an abstract class (PrScoreEditor),
which makes it easy to implement new ScoreEditors.
</para>
-
+</sect2>
</sect1>
@@ -673,9 +673,7 @@
</mediaobject>
</screenshot>
</para>
-<para>
-</para>
</sect1>
@@ -830,14 +828,14 @@
This has been replaced by proper error reporting after Brahms-1.01. If you
experience this crash, check that the following things are all right:
<itemizedlist>
-<listitem>ensure that the aRts sound server is running (you can check whether
+<listitem><para>ensure that the aRts sound server is running (you can check whether
it is running by starting artscontrol - if that works, artsd is running).
Refer to the <ulink url="http://www.arts-project.org/doc/handbook/faq.html";>
- aRts FAQ</ulink> for more information on aRts.</listitem>
-<listitem>ensure that the kdemultimedia package is installed</listitem>
-<listitem>ensure that &brahms; is installed in the same prefix KDE resides in,
+ aRts FAQ</ulink> for more information on aRts.</para></listitem>
+<listitem><para>ensure that the kdemultimedia package is installed</para></listitem>
+<listitem><para>ensure that &brahms; is installed in the same prefix KDE resides in,
for instance if KDE is installed in /opt/kde2, &brahms; should be installed
- there, too (use ./configure --prefix=/opt/kde2 during compiling)</listitem>
+ there, too (use ./configure --prefix=/opt/kde2 during
+compiling)</para></listitem>
</itemizedlist>
</para>
</answer>
@@ -897,10 +895,8 @@
<!-- TRANS:CREDIT_FOR_TRANSLATORS -->
-<para>
&underFDL;
&underGPL;
-</para>
</chapter>
@@ -948,6 +944,7 @@
<!-- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx -->
<sect1 id="description">
+<title>Description</title>
<para>
This detailed description of an installation unsing SuSE 7.3 has been contributed by
Ulrich - Thanks Ulrich, great job!
</para>
@@ -964,9 +961,9 @@
<userinput>0. Download</userinput> (e.g. to ~/download/music) and extract into a
install directory somewhere on your machine (e.g. ~/install). This is not the
path it will be installed in later:
</para>
-<para align="center">
+<screen>
uli@abraham:~/install> tar -zxvf ../download/music/brahms-1.01.tgz
-</para>
+</screen>
<para>
<userinput>1. cd to brahms-1.01</userinput>. Make sure where KDE2 is installed on
your machine. On mine, it is /opt/kde2/. Run configure with the --prefix
@@ -974,13 +971,13 @@
installation.
</para>
-<para align="center">
+<screen>
uli@abraham:~/install> cd brahms-1.01/
-</para>
+</screen>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> ./configure --prefix=/opt/kde2
--enable-debug
-</para>
+</screen>
<para>Please use the <userinput><command>--enable-debug</command></userinput> option
if you want to report bugs and stacktraces</para>
@@ -989,69 +986,69 @@
configure or make, please ask the mailing list for help. There are people who really
know what to do!
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> make
-</para>
+</screen>
<para>
<userinput>3. Now it's time to install Brahms.</userinput> Make sure that you are
root...
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> su
-</para>
+</screen>
<para>
and then run make install:
</para>
-<para align="center">
+<screen>
root@abraham:~/install/brahms-1.01> make install
-</para>
+</screen>
<para>
-<userinput>4. This should now have installed Brahms</userinput> into /opt/kde2. There
should be the Brahms executable in /opt/kde2/bin and many libBrahms*
+4. This should now have installed Brahms into /opt/kde2. There should be the Brahms
+executable in /opt/kde2/bin and many libBrahms*
libraries in /opt/kde2/lib. Feel free to check this.
</para>
<para>
-<userinput>5. Make sure that ARTS is running</userinput> by asking your system for
the artsd process
+5. Make sure that ARTS is running by asking your system for the artsd process
(you should do this as user again, not as root, because you will run Brahms as user):
</para>
-<para align="center">
+<screen>
root@abraham:~/install/brahms-1.01> exit
-</para>
-<para align="center">
+</screen>
+<screen>
uli@abraham:~/install/brahms-1.01> ps -ef | grep artsd
-</para>
+</screen>
<para>
One line of the result should be something like this:
</para>
-<para align="center">
+<screen>
uli 1036 1 0 Nov25 ? 00:00:05 /opt/kde2//bin/artsd -F 10 -S
4096 -s 60 -m artsmessage -l 3 -f
-</para>
+</screen>
<para>
If this is _not_ the case, start arts with as much debugging info as possible:
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> artsd -l0
-</para>
+</screen>
<para>
If this _is_ the case, restart arts by e.g. killing the process and restarting it
with
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> artsshell terminate
-</para>
-<para align="center">
+</screen>
+<screen>
uli@abraham:~/install/brahms-1.01> kcminit arts
-</para>
+</screen>
<para>
or (this is what I did to make sure that arts is really running the way it runs
when I start the machine 'normally') just re-login or
@@ -1064,32 +1061,32 @@
</para>
<para>
-<userinput>6. Make sure that /opt/kde2/lib is in your LD_LIBRARY_PATH</userinput>
environment variable:
+6. Make sure that /opt/kde2/lib is in your LD_LIBRARY_PATH environment variable:
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> echo LD_LIBRARY_PATH
-</para>
+</screen>
<para>
If you find /opt/kde2/lib in the result of this command, you are nearly ready to
run Brahms. If not, add it with:
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/kde2/lib
-</para>
+</screen>
<para>
-<userinput>7. Make also sure that /opt/kde2/bin is in your PATH</userinput>
environment variable (same steps as in 6, only with PATH instead of LD_LIBRARY_PATH).
+7. Make also sure that /opt/kde2/bin is in your PATH environment variable (same steps
+as in 6, only with PATH instead of LD_LIBRARY_PATH).
</para>
<para>
-<userinput>8. Start Brahms</userinput> by typing
+8. Start Brahms by typing
</para>
-<para align="center">
+<screen>
uli@abraham:~/install/brahms-1.01> Brahms &
-</para>
+</screen>
<para>
or using the Alt-F2 startup option. (The first possibility gives you more
information in case something goes wrong).
--- libltdl/ltdl.m4
+++ libltdl/ltdl.m4 2002/06/12 12:23:15
@@ -46,7 +46,7 @@
AC_REQUIRE([AC_LTDL_OBJDIR])dnl
AC_REQUIRE([AC_LTDL_DLPREOPEN])dnl
AC_REQUIRE([AC_LTDL_DLLIB])dnl
-AC_REQUIRE([AC_LTDL_SYMBOL_USCORE])dnl
+dnl AC_REQUIRE([AC_LTDL_SYMBOL_USCORE])dnl
])
AC_DEFUN(AC_LTDL_ENABLE_INSTALL,
--- brahms/core/Makefile.am.orig Sun Aug 11 22:19:23 2002
+++ brahms/core/Makefile.am Sun Aug 11 22:19:36 2002
@@ -1,4 +1,4 @@
-KDE_CXXFLAGS += -DEXAMPLES_DIR='"$(kde_datadir)/artsbuilder/examples"'
+KDE_CXXFLAGS = -DEXAMPLES_DIR='"$(kde_datadir)/artsbuilder/examples"'
APPSDIR = $(kde_appsdir)/Multimedia
# set the include path for X, qt and KDE
INCLUDES= $(all_includes) -I$(kde_includes)/arts -I$(top_srcdir)/libltdl
-I$(top_srcdir)/brahms -I$(top_builddir)/brahms/arts -I$(top_srcdir)/brahms/alsa
$(GLIB_CFLAGS)
--
Software-Engineer, Developer for Embedded Devices
Project: Pertergrin, a role playing game system
GnuPG Public Key available on request
msg71455/pgp00000.pgp
Description: PGP signature
