Help - Search - Members - Calendar
Full Version: how to compile ogg source code?
Hydrogenaudio Forums > Lossy Audio Compression > Ogg Vorbis > Ogg Vorbis - General
jianxin yan
hi.

could anyone have compiled ogg source code under win2k MSVC6.0?

yesterday i had compiled oggenc.exe and oggdrop.exe, but the whole file structure of ogg source code make me puzzled, i had to try them without aim.

would you give comments about these source code dirrectory usage?(such as AO, ogg, vorbis, ogg_phyon, win32sdk ....)



thanks.

Yan
Lear
QUOTE
Originally posted by jianxin yan
hi.

could anyone have compiled ogg source code under win2k MSVC6.0?

Yes.

QUOTE
yesterday i had compiled oggenc.exe and oggdrop.exe, but the whole file structure of ogg source code make me puzzled, i had to try them without aim.


It can be a bit confusing at first. I generally work with my own project files anyway (so that I can play with options freely).

In general, each package (see below) is available as a static .lib-file or a dynamic .dll, with or without debug code. For each combination there's a project file and bat file (that compiles that project) in the win32 folder (e.g., in vorbiswin32).

QUOTE
would you give comments about these source code dirrectory usage?(such as AO, ogg, vorbis, ogg_phyon, win32sdk ....)

ao - portable audio output library. Used by ogg123, but since ogg123 won't compile with MSVC it is of little use at the moment.

ogg - low-level bitstream packaging.

vorbis - the vorbis codec.

vorbisfile - easy file-based decoder interface.

vorbisenc - easy encoder setup interface.

ogg_python - Ogg bindings for Python (a script language).

win32sdk - Files used to build the Windows SDK, AFAIK. Haven't looked much at it.

What you really need to use Vorbis is ogg, vorbis, vorbisfile and vorbisenc, and possibly some of the tools (which use the previously mentioned modules).
jianxin yan
thanks.

i had compiled oggenc.exe and oggdrop.exe with win32-tools
and vorbis-tools.

but they also will use other directory files such as ogg and vorbis when i debug oggenc.exe.

meantime there are a lot of warning when compileing.

could you compiling to make a winamp plugin? i have tried but failed.


please give me some procedures about compiling them in details.



regards.
Yan
Lear
QUOTE
Originally posted by jianxin yan

i had compiled oggenc.exe and oggdrop.exe with win32-tools
  and vorbis-tools.

but they also will use other directory files such as ogg and vorbis when i debug oggenc.exe.


That is normal. These directories contains the core ogg and vorbis functions that e.g. oggenc uses.

QUOTE

meantime there are a lot of warning when compileing.


The warnings I've seen have been about signed/unsigned conversions, float to int conversions, etc. While they can indicate problems, they shouldn't in this case. If I use warning level 1, there are no warnings (and the code seems to work fine).

QUOTE

could you compiling to make a winamp plugin? i have tried but failed.


I haven't compiled the Winamp plugin myself. I doubt it is being maintained, so it might not be possible. I just use the plugin from http://www.blorp.com/~peter/.
john33
The Winamp2 plugin that's in the CVS is deprecated. You should use PP's plugin. It has many more features and uses the latest code anyway.

john33
jianxin yan
hi, lear and john33

The oggdrop.exe and oggenc.exe which i compiled will be surely same as such binary executive files which can be downloaded directly from john33 compiled?
does oggdrop.exe make a same *.ogg as oggdropxp.exe?


there are many .dsw and also in all.dsw there are about 9 projects, so i feel confused about so many projects.


another question, how to use so many *.bat files, i can't use them correctly. they seem to make some working directories for compile source codes,but i am not sure.

regards.
Delirium
QUOTE
Originally posted by john33
The Winamp2 plugin that's in the CVS is deprecated. You should use PP's plugin. It has many more features and uses the latest code anyway.
Is this the in_vorbis.exe that's linked from vorbis.com?
jianxin yan
QUOTE
Originally posted by Delirium
Is this the in_vorbis.exe that's linked from vorbis.com?


just now i had visited Peter'site, i guess that in_vorise.exe is what john33 refer to.


regards.
Lear
QUOTE
Originally posted by jianxin yan
hi, lear and john33

The oggdrop.exe and oggenc.exe which i compiled will be surely same as such binary executive files which can be downloaded directly from john33 compiled?
does  oggdrop.exe make a same *.ogg as oggdropxp.exe?


Yes. They both use the same ogg and vorbis code. Only the user interface differs.

QUOTE

there are many .dsw  and also in all.dsw there are about 9 projects, so i feel confused about so many projects. 


There are a couple of all.dsw, but I had a look at the one for oggdrop. You could get away with half of the projects in that one, since two versions of oggdrop are built with it. One stand-alone executable one that needs a couple of DLLs. The difference is where the "core" ogg vorbis code is located; either in oggdrop.exe (_static) or a couple of DLLs (_dynamic). See my previous post for an explanation of what the different projects does.

QUOTE

another question, how to use so many *.bat files, i can't use them correctly. they seem to make some working directories for compile source codes,but i am not sure.


You should be able to run them directly - at least if you've grabbed the sources from CVS. If you're using the source archives at xpih.org, the folder names might not be correct. They should be ogg and vorbis, not e.g. libogg-1.0rc3, for the include files to be found. Oh, you might also need to set the env-variable SRCROOT to the folder where the "ogg" and "vorbis" folders are located (if you get warnings about files missing at "i:xiph", then this is the case).
john33
Delirium,

The Winamp plugin pointed to at Vorbis.com is PP's plugin. The one that is deprecated is the source code that is in the CVS.

john33
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.