| 30 |
Instead of using POSIX calls then standard C calls will be used for file |
Instead of using POSIX calls then standard C calls will be used for file |
| 31 |
access. This applies e.g. to Windows systems. |
access. This applies e.g. to Windows systems. |
| 32 |
|
|
| 33 |
Compiling: |
Compiling |
| 34 |
========== |
========= |
|
- Use './configure && make all' to compile the library and all tools and |
|
|
demo applications. |
|
| 35 |
|
|
| 36 |
- Beside the actual library there are four applications: |
You can either compile the sources and install the library directly on |
| 37 |
|
your system or you can create Redhat or Debian packages. |
| 38 |
|
|
| 39 |
|
a) Compiling and installing directly |
| 40 |
|
|
| 41 |
|
Use 'make -f Makefile.cvs && ./configure && make' to compile the library, |
| 42 |
|
all tools, demo applications, documentation and install them with |
| 43 |
|
'make install'. You can use 'make distclean && make -f Makefile.cvs clean' |
| 44 |
|
to clean up everything again. |
| 45 |
|
|
| 46 |
|
b) Creating Debian packages |
| 47 |
|
|
| 48 |
|
Use 'make -f Makefile.cvs && dpkg-buildpackage -rfakeroot' to compile and |
| 49 |
|
create the Debian packages. This will generate 3 Debian packages: |
| 50 |
|
|
| 51 |
|
libgig: Contains the shared library files. |
| 52 |
|
libgig-dev: Contains the header files and documentation for building |
| 53 |
|
applications using libgig. |
| 54 |
|
gigtools: Contains the tools and demo applications. |
| 55 |
|
|
| 56 |
|
You can use 'fakeroot debian/rules clean && make -f Makefile.cvs clean' |
| 57 |
|
to clean up everything again. |
| 58 |
|
|
| 59 |
|
c) Creating Redhat packages |
| 60 |
|
|
| 61 |
|
You need to have the rpmbuild tool installed and properly configured to |
| 62 |
|
create RPM packages. To create the RPM packages do the following: |
| 63 |
|
|
| 64 |
|
* Get .spec file generated by ./configure and edit it as appropriate. |
| 65 |
|
|
| 66 |
|
* Copy the source tarball to "/usr/src/<rpmdir>/SOURCES" directory, |
| 67 |
|
where <rpmdir> is dependent to the system you are using. For SuSE |
| 68 |
|
<rmpdir> will be "packages", for Mandrake <rpmdir> is "RPM" and for |
| 69 |
|
Redhat / Fedora <rpmdir> always equals "redhat". |
| 70 |
|
|
| 71 |
|
* Build the rpm(s) by invoking 'rpmbuild -bb <specfile>' from the |
| 72 |
|
command line. |
| 73 |
|
|
| 74 |
|
On success, the resulting rpm(s) can usually be found under the proper |
| 75 |
|
"/usr/src/<rpmdir>/RPMS/<arch>" directory. |
| 76 |
|
|
| 77 |
|
Tools |
| 78 |
|
===== |
| 79 |
|
|
| 80 |
|
Beside the actual library there are four applications: |
| 81 |
|
|
| 82 |
gigdump: Demo app that prints out the content of a .gig file. |
gigdump: Demo app that prints out the content of a .gig file. |
| 83 |
gigextract: Extracts samples from a .gig file. |
gigextract: Extracts samples from a .gig file. |
| 85 |
rifftree: Tool that prints out the RIFF tree of an arbitrary RIFF |
rifftree: Tool that prints out the RIFF tree of an arbitrary RIFF |
| 86 |
file. |
file. |
| 87 |
|
|
| 88 |
- If you have Doxygen installed you can generate the API documentation by |
API Documentation |
| 89 |
just running 'doxygen' in the sources' top level directory. |
================= |
| 90 |
|
|
| 91 |
- 'make distclean' to clean up everything again |
If you have Doxygen installed you can generate the API documentation by |
| 92 |
|
just running 'doxygen' in the sources' top level directory. The API |
| 93 |
|
documentation will be generated in the 'html' subdirectory. |
| 94 |
|
|
| 95 |
Patches |
Patches |
| 96 |
======= |
======= |
Parent Directory
| 
Revision Log
| 
Patch