similar to: libogg 1.1.3 and libvorbis 1.1.2 releases

Hi all, Here is a patch to user pkg-config (if available) to detect libogg and fall back to old method if pkg-config fails. Pkg-config has the advantage that it can do configured to do the right thing when cross-compiling. Erik --- Makefile.am | 4 +- autogen.sh | 15 ++++++++++ configure.ac | 14 ++++++++- m4/Makefile.am | 4 ++ m4/extra_pkg.m4 | 85

Zen (and everyone else), I finally had time this weekend to review the libogg and libvorbis release status. I think both are ready to go on the linux side. There are quite a few vorbis issues open, but I don't think anything is release critical, and we should get the gcc4 aliasing bugfix out there. How are things looking with your build? Is current svn is building for you? As soon as

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

hey, i am running freebsd and i?ve got the following problem with installing icecast 2.3.1. (libxslt-1.1.0 and libogg 1.1.3 is installed) but when i am trying to install libvorbis 1.1.3 i always get this message: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Package ogg was not found in the pkg-config

> On Sat, 3 Mar 2007, Aaron Gray wrote: >> Two things regarding the new subversion repository :- >> 1) Can you remove lib/CodeGen/ELF - which was a copy of the 'libelf' GNU >> library which got partially deleted. > > I just removed it from the CVS repo. > >> 2) Is there any way make the "Win32" Visual Studio 2003 a separate source >>

I don't know. If that's all it was, why is there a special new property manager to set it? Morten will need to explain what to do in VS2003 to make VS2005 happy. Chris Lattner wrote: > On Fri, 27 Jan 2006, Jeff Cohen wrote: > >> The new property manager doesn't exist in VS2003 either. Don't know >> where to add it. > > > Isn't there a place to

On Fri, 27 Jan 2006, Jeff Cohen wrote: > The new property manager doesn't exist in VS2003 either. Don't know where to > add it. Isn't there a place to add -D_CRT_SECURE_NO_DEPRECATE for the preprocessor? Isn't this all we are talking about, or am I missing something? -Chris >> On Fri, 27 Jan 2006, Jeff Cohen wrote: >> >>> _CRT_SECURE_NO_DEPRECATE

The new property manager doesn't exist in VS2003 either. Don't know where to add it. Chris Lattner wrote: > On Fri, 27 Jan 2006, Jeff Cohen wrote: > >> _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it >> in VS2003. > > > It shouldn't hurt to define it though, even if VC2003 where it does > nothing. Right? > > -Chris >

_CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in VS2003. Morten Ofstad wrote: > Jeff Cohen wrote: > >> The project files need frequent updating. I cannot maintain VS2005 >> project files, so while they could be distributed with LLVM, they >> will become broken fast. Also, VS2003 and VS2005 project and >> solution files cannot coexist in

On Fri, 27 Jan 2006, Jeff Cohen wrote: > _CRT_SECURE_NO_DEPRECATE is new for VS2005. Nothing I can do with it in > VS2003. It shouldn't hurt to define it though, even if VC2003 where it does nothing. Right? -Chris > Morten Ofstad wrote: > >> Jeff Cohen wrote: >> >>> The project files need frequent updating. I cannot maintain VS2005 >>>

Michael Grigoni wrote: >> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> Package ogg was not found in the pkg-config search path. >> Perhaps you should add the directory containing `ogg.pc' >> to the PKG_CONFIG_PATH environment variable My previous post was somehow mangled: Here

Jeff Cohen wrote: > The project files need frequent updating. I cannot maintain VS2005 > project files, so while they could be distributed with LLVM, they will > become broken fast. Also, VS2003 and VS2005 project and solution files > cannot coexist in the same directories, further complicating matters. The VS2003 project files convert without problems -- you might want to add in

On Sat, 3 Mar 2007, Aaron Gray wrote: >> What is the motivation for this? The Win32 directory doesn't have VS2003 >> source code AFAIK, > > No just the VS2003 project and solution files and a about 30 sub directories > which are not required on *nix platforms. So it would be good to have the > "win32" files in a separate repository if possible. I thought this

Michael Grigoni wrote: > >>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>> Package ogg was not found in the pkg-config search path. >>> Perhaps you should add the directory containing `ogg.pc' >>> to the PKG_CONFIG_PATH environment variable > > My previous

Ok! If there are indeed cross-compiling targets defined, then vs2005 projects probably should be maintained. In any case, this is all up to Jean-Marc, since he's the one that actually has authority to change it :) Jean-Marc -- what's your opinion? On 11/28/07, Aron Rosenberg <arosenberg@sightspeed.com> wrote: > > I pulled the test directory from 2003, but everything else

On Sat, 3 Mar 2007, Aaron Gray wrote: > Two things regarding the new subversion repository :- > 1) Can you remove lib/CodeGen/ELF - which was a copy of the 'libelf' GNU > library which got partially deleted. I just removed it from the CVS repo. > 2) Is there any way make the "Win32" Visual Studio 2003 a separate source > repository, so we do not have the VS2003

> On Sat, 3 Mar 2007, Aaron Gray wrote: >>> What is the motivation for this? The Win32 directory doesn't have >>> VS2003 >>> source code AFAIK, >> >> No just the VS2003 project and solution files and a about 30 sub >> directories >> which are not required on *nix platforms. So it would be good to have the >> "win32" files

Hello, I maintain audio processing part of code in sipXtapi -- open-source VoIP library. And when I engaged Speex library, I found that its Windows project files are not up to date and use strange settings. They miss several source files and use single-threaded static runtime libraries. I see no benefits of using static and moreover single-threaded libraries. In the modern world very small amount