/[svn]/libgig/trunk/README
ViewVC logotype

Diff of /libgig/trunk/README

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1062 by schoenebeck, Thu Oct 19 19:01:13 2006 UTC revision 1063 by schoenebeck, Sat Mar 3 21:45:25 2007 UTC
# Line 48  Requirements Line 48  Requirements
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    
# Line 107  Compiling Line 118  Compiling
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      libgig and its tools can be compiled for Windows using Bloodshed Dev-C++,
124      which is a free (GPL) C++ integrated development environment for Windows.
125      You can download it here:
126    
127        http://www.bloodshed.net/devcpp.html
128    
129      Make sure you install a version with Mingw integrated.
130    
131      a) Compiling libgig.dll
132    
133      Simply open the project file "win32/libgig.dev" either directly in Dev-C++
134      or by double clicking on the project file in the Windows explorer, then
135      click on "Compile" in the Dev-C++ menu and that's it! After compilation
136      finished, you can find the files "libgig.dll", "libgig.a" and
137      "liblibgig.def" in the "win32" directory.
138    
139      b) Compiling the example tools "rifftree", "dlsdump" and "gigdump"
140    
141      You need to have libgig.dll compiled as described in a). Then you can
142      compile the respective tool by simply opening the respective project
143      (.dev) file and clicking on "Compile" from the Dev-C++ menu. After
144      compilation you can find the respective .exe file in the "win32"
145      directory.
146    
147      c) Compiling the example tool "gigextract"
148    
149      You need to have libgig.dll compiled as described in a). Also you need
150      libsndfile (as DLL) which is used to create the .wav files. You can
151      download libsndfile already precompiled as DLL here:
152    
153        http://www.mega-nerd.com/libsndfile/
154    
155      Extract the .zip file i.e. to "C:\". The libsndfile .dll file should then
156      be i.e. under "C:\libsndfile-1_0_17". Beside the .dll file, make sure
157      libsndfile's .lib file exists in that directory as well. If the .lib file
158      does not exist yet, you have to create it with:
159    
160        dlltool --input-def libsndfile-1.def --output-lib libsndfile-1.lib
161    
162      Then you have to ensure the settings of gigextract's Dev-C++ project file
163      are pointing to the correct location of your local copy of libsndfile. For
164      that click in the Dev-C++ menu on "Project" -> "Project Options". Then
165      click on the tab "Parameter" and make sure the path to "libsndfile-1.lib"
166      in the "Linker" list view is correct. Then click on the tab "Directories"
167      and then on the tab "Include Directories" and make sure the path to
168      libsndfile points to the correct location there as well.
169    
170      After that you should finally be able to compile "gigextract" by clicking
171      on "Compile" in the Dev-C++ menu. After compilation succeeded, you can
172      find the "gigextract.exe" file in the "win32" directory.
173    
174  Test Cases  Test Cases
175  ==========  ==========
176    The libgig sources come with a tiny console application which allows to    The libgig sources come with a tiny console application which allows to

Legend:
Removed from v.1062  
changed lines
  Added in v.1063

  ViewVC Help
Powered by ViewVC