9 |
files and provide abstract access to the |
files and provide abstract access to the |
10 |
data. |
data. |
11 |
- gig classes (gig.h, gig.cpp): These are based on the DLS classes and |
- gig classes (gig.h, gig.cpp): These are based on the DLS classes and |
12 |
provide the neccessary extensions for |
provide the necessary extensions for |
13 |
the Gigasampler file format. |
the Gigasampler file format. |
14 |
|
|
15 |
Requirements |
Requirements |
21 |
autoconf 2.57 |
autoconf 2.57 |
22 |
|
|
23 |
If you want to compile the 'gigextract' application that comes with these |
If you want to compile the 'gigextract' application that comes with these |
24 |
sources then you will additionally need to have libaudiofile installed (I |
sources then you will additionally need to have libaudiofile (>= 0.2.3) |
25 |
used version 0.2.3). |
or libsndfile (>= 1.0.2) installed. Note: for Windows systems only |
26 |
|
libsndfile is available. |
27 |
|
|
28 |
Non-POSIX systems |
Non-POSIX systems |
29 |
================= |
================= |
46 |
|
|
47 |
b) Creating Debian packages |
b) Creating Debian packages |
48 |
|
|
49 |
Use 'make -f Makefile.cvs && dpkg-buildpackage -rfakeroot' to compile and |
Use 'make -f Makefile.cvs && dpkg-buildpackage -rfakeroot -b' to compile |
50 |
create the Debian packages. This will generate 3 Debian packages: |
and create the Debian packages. This will generate 3 Debian packages: |
51 |
|
|
52 |
libgig: Contains the shared library files. |
libgig: Contains the shared library files. |
53 |
libgig-dev: Contains the header files and documentation for building |
libgig-dev: Contains the header files and documentation for building |
59 |
|
|
60 |
c) Creating Redhat packages |
c) Creating Redhat packages |
61 |
|
|
62 |
TODO |
You need to have the rpmbuild tool installed and properly configured to |
63 |
|
create RPM packages. To create the RPM packages do the following: |
64 |
|
|
65 |
|
* Get .spec file generated by ./configure and edit it as appropriate. |
66 |
|
|
67 |
|
* Copy the source tarball to "/usr/src/<rpmdir>/SOURCES" directory, |
68 |
|
where <rpmdir> is dependent to the system you are using. For SuSE |
69 |
|
<rmpdir> will be "packages", for Mandrake <rpmdir> is "RPM" and for |
70 |
|
Redhat / Fedora <rpmdir> always equals "redhat". |
71 |
|
|
72 |
|
* Build the rpm(s) by invoking 'rpmbuild -bb <specfile>' from the |
73 |
|
command line. |
74 |
|
|
75 |
|
On success, the resulting rpm(s) can usually be found under the proper |
76 |
|
"/usr/src/<rpmdir>/RPMS/<arch>" directory. |
77 |
|
|
78 |
Tools |
Tools |
79 |
===== |
===== |
90 |
================= |
================= |
91 |
|
|
92 |
If you have Doxygen installed you can generate the API documentation by |
If you have Doxygen installed you can generate the API documentation by |
93 |
just running 'doxygen' in the sources' top level directory. The API |
running 'make docs' in the sources' top level directory. The API |
94 |
documentation will be generated in the 'html' subdirectory. |
documentation will be generated in the 'doc' subdirectory. |
95 |
|
|
96 |
Patches |
Patches |
97 |
======= |
======= |