I decided, since nobody else seems to be doing it, to do a new build of the Mac library. Unfortunately, things now rely on os_types.h. No problem, I'll just create an os_types.h in mac/compat. Except os.h #includes "../include/vorbis/os_types.h" -- in other words, it explicitly wants the os_types.h that was generated from os_types.h.in by configure. The simple solution is to just #include "os_types.h" in os.h and make sure include/vorbis is in the compiler's include path on Unix platforms. It is already, isn't it? Maybe just include, so you'd have to #include "vorbis/os_types.h" -- this isn't a big deal for me on the Mac either, as all I have to do is create a vorbis folder in side mac/compat and stick my os_types.h in there. And now, a general word of advice. Every little thing that relies on autoconf/configure makes it harder to port the Vorbis reference implementation to the two platforms that make up 99% of the desktop market. Please, think very hard about whether what you want to do can be done without platform-specific configuration tools before using them. -- Chris Hanson bDistributed.com, Inc. cmh@bDistributed.com --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> And now, a general word of advice. Every little thing that relies on > autoconf/configure makes it harder to port the Vorbis reference > implementation to the two platforms that make up 99% of the desktop > market. Please, think very hard about whether what you want to do > can be done without platform-specific configuration tools before > using them.I use autoconf and automake with icecast tools without problems for the win32 side. The way I have done this is do: #ifdef _WIN32 #include <win32config.h> #else #include <config.h> #endif config.h does all the necessary defines from configure, etc. And win32 config.h is the set for all win32 systems. Works great. Also, you can use autoconf and automake in win32, using the cygnus build tools. I usually use MSVC for win32 development (as does most of the win32 world) so I don't use them. So the only platform which doesn't have autoconf/automake is the legacy Mac OS. Mac OSX does just fine with these tools. It would be trivial to do this all in os.h with #ifdef _MAC #include <macconfig.h> #else #ifdef _WIN32 #include <win32config.h> #else #include <config.h> #endif #endif or something. jack. --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
> I decided, since nobody else seems to be doing it, to do a new build > of the Mac library. > > Unfortunately, things now rely on os_types.h. No problem, I'll just > create an os_types.h in mac/compat. Except os.h #includes > "../include/vorbis/os_types.h" -- in other words, it explicitly wants > the os_types.h that was generated from os_types.h.in by configure.Actually, one can just copy the os_types.h.in to os_types.h. I'm working on an automated way of CVS doing that at checkout.> And now, a general word of advice. Every little thing that relies on > autoconf/configure makes it harder to port the Vorbis reference > implementation to the two platforms that make up 99% of the desktop > market. Please, think very hard about whether what you want to do > can be done without platform-specific configuration tools before > using them.This was an oversight and yet another concession to autoconf, a tool I'm learning to hate with a passion more and more as the years roll on... It handles 'dealing with types' very poorly and only through convoluted hacks, and the change represents a considerable clenliness improvement on the UNIX side. Windows also needs the copy hack. (simply checking a copied version into CVS won't last because when configure runs, it will be modified, and the next checkin will blast the copied version if the programmer forgets to delete the generated one by accident). (Also, that was not a troll/invitation to defend autoconf, just my personal feelings about it). Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-dev-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.