Hello folks, So as it turns out (having gotten sucked into virtualization development at Red Hat) I'm now actually pretty well set up to handle some amount of Windows build system maintenance and binary builds for relases. Of course simply having the tools (and not having even tried to use them since.. oh around 1998) doesn't mean I know what I'm doing. I know we have Win32 capable volunteers, and I'd appreciate some help getting up to speed as well as general contributions both getting win32 builds fixed up for the upcoming libvorbis release, but also deciding on a build system policy for Win32 in general. Specifically 'which versions of the project files shall we officially support? Or do we just decide to ship nmake?' etc. Help and input appreciated. Thanks, Monty
On Thu, Apr 2, 2009 at 10:21 PM, Christopher Montgomery <xiphmont at gmail.com> wrote:> Hello folks, > > So as it turns out (having gotten sucked into virtualization > development at Red Hat) I'm now actually pretty well set up to handle > some amount of Windows build system maintenance and binary builds for > relases. ?Of course simply having the tools (and not having even tried > to use them since.. ?oh around 1998) doesn't mean I know what I'm > doing. > > I know we have Win32 capable volunteers, and I'd appreciate some help > getting up to speed as well as general contributions both getting > win32 builds fixed up for the upcoming libvorbis release, but also > deciding on a build system policy for Win32 in general. ?Specifically > 'which versions of the project files shall we officially support? ?Or > do we just decide to ship nmake?' etc.Mingw32 ftw!
On Thu, Apr 2, 2009 at 7:21 PM, Christopher Montgomery <xiphmont at gmail.com> wrote:> I know we have Win32 capable volunteers, and I'd appreciate some help > getting up to speed as well as general contributions both getting > win32 builds fixed up for the upcoming libvorbis release, but also > deciding on a build system policy for Win32 in general. ?Specifically > 'which versions of the project files shall we officially support? ?Or > do we just decide to ship nmake?' etc.So Christian Adam, who's maintaining the dshow filters, bought a real copy of VS2005. Since the project file format is pretty much identical to 2008, the plan is to support VS2005, and people with 2008 can just convert. He has to use the real version so he can build for the mobile targets, which aren't supported by the gratis express edition. So that's the primary target. I don't know if VC6 support is still important to anyone. Maintaining an nmake or xmingw32 build is optional. (I actually had good luck with derf's xmingw32 makefiles for theora; I was thinking about adding something similar for ogg and vorbis just to simplify generating the dependencies for that.) My recommendation is to remove the VC6 and VS2003 build directories, verify the VS2005 project files work, and leave it at that. -r
Ralph Giles wrote:> Maintaining an nmake or xmingw32 build is optional.I keep an eye on libogg and libvorbis and make sure that Linux -> Win32 cross compiles stay working. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/
On Fri, Apr 3, 2009 at 12:18 AM, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote:> I keep an eye on libogg and libvorbis and make sure that Linux -> Win32 > cross compiles stay working.Do you have instructions for this? Do you use the autoconf build somehow, or is this a custom makefile? -r
Ralph Giles wrote:> Do you have instructions for this?cd libXXXX svn up ./autogen.sh --host=i586-mingw32msvc \ --target=i586-pc-mingw32msvc --build=x86_64-linux make check The tests run under Wine quite happily. If I remember correctly, I did have to upgrade libtool which was broken in Ubuntu 8.10. I just grabbed the debian source package from Ubuntu jaunty and installed that. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/
> 'which versions of the project files shall we officially support?Mingw32 please. Supporting VS version zillion.1 is a moving target (like all stuff from Redmond) with few concessions to compatibilty and substantial obfuscation.