search for: metrowerks

...which is strange. Presumably, this is a problem with the MrC compiler (which is unfortunate, generally it's code generation is very good!), so I'm planning to shell out some bucks for a CodeWarrior seat just so I can build this library. I guess my real question is simply "does the Metrowerks compiler build libogg/libvorbis on this platform correctly?". The libraries that "ship" in the classic MacOS Vorbis SDK are toast, which doesn't inspire confidence, but it looks like perhaps it's just some kind of export configuration problem. Is there anyone out there wh...

...'t find MacTypes.h in the path. MacTypes.h is simply a one line file that includes <CoreServices/CoreServices.h>, so I just replaced the MacTypes.h with that. In addition, sys_types.h was attempting to include <alloca.h>, which doesn't seem to exist. Is that only included with MetroWerks? I'm using PB/GCC. Brian Hook, President Pyrogon, Inc. <p>--- >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 'uns...

Hello list, (PC Windows 2000, R 1.2.3) i want to compile C source file for R on windows 2000. I'm working with Metrowerks CodeWarrior for creating and compiling C files. I've see that R.lib file must be obtain with R.ddl by Visual C++. I don't have Visual C++ (and i don't want to buy it !!) but i want to obtain R.lib file. Is there a solution to my problem ??? Any help would be greatly appreciated. --...

I have a zip file containing updated Macintosh support for Vorbis on my company's web site at the following URL: http://bDistributed.com/projects/vorbis-mac/MacVorbisUpdatesBeta3.zip I used Metrowerks ClassWrangler to build the file because StuffIt insisted on MacBinary-encoding the project files. StuffIt Expander seems to have issues with expanding it, so I'm not sure if it's OK or not. For the other Mac developers I put a StuffIt 5 archive at http://bDistributed.com/projects/v...

...some indicate real bugs. In particular it seems likely we have more unitialized variables since Dan reports differing encoder output depending on the compiler used. In general, we need to go through the warnings and look for real problems on whatever platforms we have access to. gcc, msvc and metrowerks codewarrior are a good start. It's good to remove them when we can even if they're not bugs to clean up the output, but note that by policy we disregard some, such as those warning about using standard C implicit type conversion. -r <p> -------------- next part -------------- A...

Hey, I ran across this while building vorbis on the Mac: In libvorbis RC2, file info.c, line 65, there's a call to strdup(). strdup() isn't portable, and it looks like the code should use the internal memory functions to create the memory for the string anyway. Actually, on further inspection, it looks like the memory for the user comments is never actually freed. I'm not subscribed

Full_Name: Martin Gansser Version: 1.5.1 OS: hp-ux 11.00 Submission from: (NULL) (195.145.22.147) cc -Wp,-H16000 -I. -I../../../src/include -I../../../src/include -I/opt/gnome/include/gnome-1.0 -DNE ED_GNOMESUPPORT_H -I/opt/gnome/lib/gnome-libs/include -I/opt/gnome/include/glib-1.2 -I/opt/gnome/lib /glib/include -I/opt/gnome/include/orbit-1.0 -I/opt/gnome/include/gtk-1.2

Well, I updated the player to work with the branch_postbeta2, but it contains some nasty kludges to the project files that probably shouldn't be finalized. I'm going to put it in a separate file (http://oscar.the-rileys.net/programming/vorbis_pb2.tar.gz) for now. Unfortunately, this release doesn't seem to fix the "tearing sound" problem. I think this might be related to

Thanks for the http://vorbis.com link. That worked. But I looked in the download area and there is no SDK for Mac OS 9. So I am compiling the vorbis code directly into my app. The problem I am having now is that the CodeWarrior 5.0 compiler has a bug with alloca(). It allocates the area on the stack but, under some circumstances, it does not restore the stack pointer at the end of the routine.

...tries to do, Huh? Intel CC supports the MSVC++ ABI. Zortech (Digital Mars) supports it, too (though the guy who wrote it isn't too proud of that fact--or the fact that he even wrote that compiler to begin with). Heck, even CodeWarrior supported it (as Howard Hinnant might well remember), before Metrowerks sold off their x86 compiler backend. In fact, other than GCC, only Borland and Watcom don't support it, and that's only because they originally developed theirs during the DOS era, before MSVC++ became the de facto standard compiler. (But Watcom also used to support MFC development on Windo...

> Right. What's the point of all the effort devoted to MSVC++ ABI > compatibility when Clang doesn't need it for being a top-notch C++ > compiler on Windows? I brought up a similar point a little bit earlier, too.... It seems like the only necessary condition for being a first-class native-code development tool on Windows is to support the platform C ABI and the subset of the

Duncan Sands <baldrick at free.fr> writes: > On 29/07/13 15:30, Anton Korobeynikov wrote: >>>> object in place on the stack or at least call its copy constructor. >>> >>> >>> what does GCC do? >> Nothing. It does not support MSVC ABI. > > Maybe we shouldn't either :) Right. What's the point of all the effort devoted to MSVC++

Colin Farrow <C.Farrow@geology.gla.ac.uk> writes: > Peter, > > Cautiously sticking my neck above the water line here. I have been > wondering about the Mac version for a while now. I may be able to get > an MSc IT student to work on this as a project for about 3 months > June-Sept. Before putting up the proposal some idea of the scale of the > task would be useful. Do

...tel CC supports the MSVC++ ABI. Zortech (Digital Mars) supports > it, too (though the guy who wrote it isn't too proud of that fact--or > the fact that he even wrote that compiler to begin with). Heck, even > CodeWarrior supported it (as Howard Hinnant might well remember), > before Metrowerks sold off their x86 compiler backend. In fact, other > than GCC, only Borland and Watcom don't support it, and that's only > because they originally developed theirs during the DOS era, before > MSVC++ became the de facto standard compiler. (But Watcom also used to > support MFC...

...comments to clibpdf@fastio.com. ## Platforms tested so far -- Unix variants -- BSDI BSD/OS 3.1 (gcc 2.7.2.1) FreeBSD 2.2.7-STABLE (gcc 2.7.2.1) Linux 2.0.34 (Red Hat 5.1) (gcc 2.7.2.3) MacOS X Server (Rhapsody DR2) NEXTSTEP 3.2, 3.3, OPENSTEP 4.2 SunOS 5.4 / (SUNWspro/SC4.0) -- PCs -- MacOS 8.1 (Metrowerks IDE 1.7.4) -- See also: README.MacOS8 Windows NT 4.0 (VC++ 5.0) -- See also: README.win32 ## Relationships to other software Conceptually, ClibPDF has been inspired by Cgraph for PostScript (<http://totoro.berkeley.edu/software/A_Cgraph.html), but it is much more powerful and no code from Cgra...

Looking through the archives I have seen talk of making CPU specific optimisations for Vorbis, a la MMX/3DNow!/SSE. The feeling I gather is to wait until something is working well in C before committing to any kind of specific optimisation. What if oft used and needed DSP functions were identified and standardised DSP functionality be written for Vorbis? This would seperate the basically

...ob Dellaca) +- add support for C++Builder 3 and Delphi 3 in contrib/delphi2 (Davide Moretti) +- do not exit prematurely in untgz if 0 at start of block (Magnus Holmgren) +- use macro EXTERN instead of extern to support DLL for BeOS (Sander Stoks) +- added a FAQ file + +- Support gzdopen on Mac with Metrowerks (Jason Linhart) +- Do not redefine Byte on Mac (Brad Pettit & Jason Linhart) +- define SEEK_END too if SEEK_SET is not defined (Albert Chin-A-Young) +- avoid some warnings with Borland C (Tom Tanner) +- fix a problem in contrib/minizip/zip.c for 16-bit MSDOS (Gilles Vollant) +- emulate utime()...