| 48 |
Makefile.in, etc.) then you need to have automake (>= 1.5) and autoconf |
Makefile.in, etc.) then you need to have automake (>= 1.5) and autoconf |
| 49 |
installed. |
installed. |
| 50 |
|
|
| 51 |
Non-POSIX systems (e.g. Windows): |
Windows: |
| 52 |
--------------------------------- |
-------- |
| 53 |
|
|
| 54 |
If you don't have a POSIX system, you have to set 'POSIX' to '0' in RIFF.h. |
The precompiled versions of libgig (and its tools) should be compatible |
| 55 |
Instead of using POSIX calls then standard C calls will be used for file |
with any Windows operating system of at least Win95 or younger. Notice |
| 56 |
access. This applies e.g. to Windows systems. I would appreciate if |
that all example / demo applications coming with libgig are pure console |
| 57 |
somebody sends me his MS Visual Studio / .NET, Borland C++ Builder or |
applications, thus you won't see a GUI showing up! :) |
| 58 |
Apple XCode project file! This might help others to conveniently compile |
|
| 59 |
libgig on those platforms as well. |
If you want to compile libgig and its tools by yourself, please also |
| 60 |
|
notice the requirements under "Compiling for Windows". |
| 61 |
|
|
| 62 |
|
Other Operating Systems: |
| 63 |
|
------------------------ |
| 64 |
|
|
| 65 |
|
libgig was written to compile for any operating system, using standard C |
| 66 |
|
library functions. However the latest versions of libgig lack a portable |
| 67 |
|
implementation of one tiny method called RIFF::File::ResizeFile(). So you |
| 68 |
|
would either have to add native OS API calls for that particular method, |
| 69 |
|
that is dependant to your OS, or you have to add a portable |
| 70 |
|
implementation. No matter which way you choose, please let us know! :) |
| 71 |
|
|
| 72 |
Compiling |
Compiling for Linux |
| 73 |
========= |
=================== |
| 74 |
You can either compile the sources and install the library directly on |
You can either compile the sources and install the library directly on |
| 75 |
your system or you can create Redhat or Debian packages. |
your system or you can create Redhat or Debian packages. |
| 76 |
|
|
| 118 |
On success, the resulting rpm(s) can usually be found under the proper |
On success, the resulting rpm(s) can usually be found under the proper |
| 119 |
"/usr/src/<rpmdir>/RPMS/<arch>" directory. |
"/usr/src/<rpmdir>/RPMS/<arch>" directory. |
| 120 |
|
|
| 121 |
|
Compiling for Windows |
| 122 |
|
===================== |
| 123 |
|
|
| 124 |
|
libgig and its tools can be compiled for Windows using Bloodshed Dev-C++, |
| 125 |
|
which is a free (GPL) C++ integrated development environment for Windows. |
| 126 |
|
It is also possible to use MSYS from MinGW, which allows you to use |
| 127 |
|
'./configure && make' like the linux builds. |
| 128 |
|
|
| 129 |
|
You can download Dev-C++ here: |
| 130 |
|
|
| 131 |
|
http://www.bloodshed.net/devcpp.html |
| 132 |
|
|
| 133 |
|
Make sure you install a version with Mingw integrated. |
| 134 |
|
|
| 135 |
|
a) Compiling libgig.dll |
| 136 |
|
|
| 137 |
|
Simply open the project file "win32/libgig.dev" either directly in Dev-C++ |
| 138 |
|
or by double clicking on the project file in the Windows explorer, then |
| 139 |
|
click on "Compile" in the Dev-C++ menu and that's it! After compilation |
| 140 |
|
finished, you can find the files "libgig.dll", "libgig.a" and |
| 141 |
|
"liblibgig.def" in the "win32" directory. |
| 142 |
|
|
| 143 |
|
b) Compiling the example tools "rifftree", "dlsdump" and "gigdump" |
| 144 |
|
|
| 145 |
|
You need to have libgig.dll compiled as described in a). Then you can |
| 146 |
|
compile the respective tool by simply opening the respective project |
| 147 |
|
(.dev) file and clicking on "Compile" from the Dev-C++ menu. After |
| 148 |
|
compilation you can find the respective .exe file in the "win32" |
| 149 |
|
directory. |
| 150 |
|
|
| 151 |
|
c) Compiling the example tool "gigextract" |
| 152 |
|
|
| 153 |
|
You need to have libgig.dll compiled as described in a). Also you need |
| 154 |
|
libsndfile (as DLL) which is used to create the .wav files. You can |
| 155 |
|
download libsndfile already precompiled as DLL here: |
| 156 |
|
|
| 157 |
|
http://www.mega-nerd.com/libsndfile/ |
| 158 |
|
|
| 159 |
|
Extract the .zip file i.e. to "C:\". The libsndfile .dll file should then |
| 160 |
|
be i.e. under "C:\libsndfile-1_0_17". Beside the .dll file, make sure |
| 161 |
|
libsndfile's .lib file exists in that directory as well. If the .lib file |
| 162 |
|
does not exist yet, you have to create it with: |
| 163 |
|
|
| 164 |
|
dlltool --input-def libsndfile-1.def --output-lib libsndfile-1.lib |
| 165 |
|
|
| 166 |
|
Then you have to ensure the settings of gigextract's Dev-C++ project file |
| 167 |
|
are pointing to the correct location of your local copy of libsndfile. For |
| 168 |
|
that click in the Dev-C++ menu on "Project" -> "Project Options". Then |
| 169 |
|
click on the tab "Parameter" and make sure the path to "libsndfile-1.lib" |
| 170 |
|
in the "Linker" list view is correct. Then click on the tab "Directories" |
| 171 |
|
and then on the tab "Include Directories" and make sure the path to |
| 172 |
|
libsndfile points to the correct location there as well. |
| 173 |
|
|
| 174 |
|
After that you should finally be able to compile "gigextract" by clicking |
| 175 |
|
on "Compile" in the Dev-C++ menu. After compilation succeeded, you can |
| 176 |
|
find the "gigextract.exe" file in the "win32" directory. |
| 177 |
|
|
| 178 |
Test Cases |
Test Cases |
| 179 |
========== |
========== |
| 180 |
The libgig sources come with a tiny console application which allows to |
The libgig sources come with a tiny console application which allows to |
Parent Directory
| 
Revision Log
| 
Patch