README 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134
  1. ********************************************************************
  2. * *
  3. * THIS FILE IS PART OF THE OggVorbis SOFTWARE CODEC SOURCE CODE. *
  4. * USE, DISTRIBUTION AND REPRODUCTION OF THIS LIBRARY SOURCE IS *
  5. * GOVERNED BY A BSD-STYLE SOURCE LICENSE INCLUDED WITH THIS SOURCE *
  6. * IN 'COPYING'. PLEASE READ THESE TERMS BEFORE DISTRIBUTING. *
  7. * *
  8. * THE OggVorbis SOURCE CODE IS (C) COPYRIGHT 1994-2002 *
  9. * by the Xiph.Org Foundation http://www.xiph.org/ *
  10. * *
  11. ********************************************************************
  12. WHAT'S HERE:
  13. This source distribution includes libogg and nothing else. Other modules
  14. (eg, the modules vorbis, vorbis-tools and vorbis-plugins for the Vorbis
  15. codec) contain the codec libraries for use with Ogg bitstreams.
  16. Directory:
  17. ./src The source for libogg, a BSD-license inplementation of
  18. the public domain Ogg bitstream format
  19. ./include Library API headers and codebooks
  20. ./doc Ogg specification documents
  21. ./win32 Win32 projects and build automation
  22. ./macosx MacOS X project and build files
  23. ./macos Classic MacOS 9 projects and build automation
  24. ./debian Rules/spec files for building Debian .deb packages
  25. (may not be present, depending on your distribution)
  26. WHAT IS OGG?:
  27. Ogg project codecs use the Ogg bitstream format to arrange the raw,
  28. compressed bitstream into a more robust, useful form. For example,
  29. the Ogg bitstream makes seeking, time stamping and error recovery
  30. possible, as well as mixing several sepearate, concurrent media
  31. streams into a single physical bitstream.
  32. CONTACT:
  33. The Ogg homepage is located at 'http://www.xiph.org/ogg/'.
  34. Up to date technical documents, contact information, source code and
  35. pre-built utilities may be found there.
  36. BUILDING FROM REPOSITORY SOURCE:
  37. A standard svn build should consist of nothing more than:
  38. ./autogen.sh
  39. make
  40. and as root if desired :
  41. make install
  42. This will install the Ogg libraries (static and shared) into
  43. /usr/local/lib, includes into /usr/local/include and API manpages
  44. (once we write some) into /usr/local/man.
  45. BUILDING FROM TARBALL DISTRIBUTIONS:
  46. ./configure
  47. make
  48. and optionally (as root):
  49. make install
  50. BUILDING RPMS:
  51. RPMs may be built by:
  52. make dist
  53. rpm -ta libogg-<version>.tar.gz
  54. BUILDING ON WIN32:
  55. Use the project file in the win32 directory. It should compile out of the box.
  56. You can also run one of the batch files from the commandline.
  57. E.g.: build_ogg_dynamic
  58. CROSS COMPILING FROM LINUX TO WIN32:
  59. It is also possible to cross compile from Linux to windows using the MinGW
  60. cross tools and even to run the test suite under Wine, the Linux/*nix
  61. windows emulator.
  62. On Debian and Ubuntu systems, these cross compiler tools can be installed
  63. by doing:
  64. sudo apt-get mingw32 mingw32-binutils mingw32-runtime wine
  65. Once these tools are installed its possible to compile and test by
  66. executing the following commands:
  67. ./configure --host=i586-mingw32msvc --target=i586-mingw32msvc \
  68. --build=i586-linux
  69. make
  70. make check
  71. The above has been tested with the following versions of the tools on
  72. Ubuntu's Hardy Heron release:
  73. mingw32 4.2.1.dfsg-1ubuntu1
  74. mingw32-binutils 2.17.50-20070129.1-1
  75. mingw32-runtime 3.13-1
  76. wine 0.9.59-0ubuntu4
  77. BUILDING ON MACOS 9:
  78. Ogg on MacOS 9 is built using CodeWarrior 5.3. To build it, first
  79. open ogg/mac/libogg.mcp, switch to the "Targets" pane, select
  80. everything, and make the project. In ogg/mac/Output you will now have
  81. both debug and final versions of Ogg shared libraries to link your
  82. projects against.
  83. To build a project using Ogg, add access paths to your CodeWarrior
  84. project for the ogg/include and ogg/mac/Output folders. Be sure that
  85. "interpret DOS and Unix paths" is turned on in your project; it can be
  86. found in the "access paths" pane in your project settings. Now simply
  87. add the shared libraries you need to your project (OggLib at least)
  88. and #include "ogg/ogg.h" wherever you need to acces Ogg functionality.
  89. (Build instructions for Ogg codecs such as vorbis are similar and may
  90. be found in those source modules' README files)
  91. $Id$