113 |
|
|
114 |
<a name="build_backend"></a> |
<a name="build_backend"></a> |
115 |
<h3>3. Building the Backend</h3> |
<h3>3. Building the Backend</h3> |
116 |
Grab the source code files of libgig (e.g. from our CVS server, as |
Grab the source code files of libgig (e.g. from our Subversion server, as |
117 |
described on the |
described on the |
118 |
<a href="http://linuxsampler.org/downloads.html">downloads site</a>). Then you |
<a href="http://linuxsampler.org/downloads.html">downloads site</a>). Then you |
119 |
should optimize the compilation flags for your machine. This really depends |
should optimize the compilation flags for your machine. This really depends |
176 |
<br> |
<br> |
177 |
And that's it!</br> |
And that's it!</br> |
178 |
<br> |
<br> |
179 |
The good thing: if you grabbed the sources of libgig and LS from CVS, you only |
The good thing: if you grabbed the sources of libgig and LS from Subversion, you only |
180 |
have to call: |
have to call: |
181 |
<pre> |
<pre> |
182 |
cvs update |
svn update |
183 |
dpkg-buildpackage -rfakeroot -b |
dpkg-buildpackage -rfakeroot -b |
184 |
</pre> |
</pre> |
185 |
once in a while from the source directory to conveniently compile the latest |
once in a while from the source directory to conveniently compile the latest |
186 |
version with your personal optimizations and configuration parameters for |
version with your personal optimizations and configuration parameters for |
187 |
your system, because "cvs update" updates your local source files to the |
your system, because "svn update" updates your local source files to the |
188 |
latest bleeding edge version from our CVS server but won't touch your |
latest bleeding edge version from our Subversion server but won't touch your |
189 |
modifications! |
modifications! |
190 |
<br> |
<br> |
191 |
The problematic part is to find good compile time options for your specific |
The problematic part is to find good compile time options for your specific |