Re: [Plib-users] Building Plib on Mac OSX (Darwin)
Brought to you by:
sjbaker
From: Sebastian U. <ud...@ha...> - 2001-12-28 20:46:00
|
On Fri, 28 Dec 2001, re...@ze... (Reed Hedges) wrote: > Date: Fri, 28 Dec 2001 15:16:12 -0500 > To: pli...@li... > From: re...@ze... (Reed Hedges) > Subject: Re: [Plib-users] Building Plib on Mac OSX (Darwin) [...] > 2. remove "-O6" from CXXFLAGS and CFLAGS in the Makefile ??? where did > this come from ??? The "-O6" stuff was removed recently in CVS. > 2. changed some #include statements accordingly: > from <GL/foo.h> to <OpenGL/foo.h> > from <ag.h> to <AGL/agl.h> > from <CodeFragments.h> in util/ul.h to > <CoreServices/CoreServices.h>. I also added #include <unistd.h> to > util/ul.h after CoreServices (for the sleep() function) I think we should add some more #ifdefs to the code so that PLIB automatically includes the correct header files on Mac OS X. > 3. add -Dmacintosh to DEFS in the Makefile. Hmm ... you had to do this manually ? We have to find a way to determine whether the machine we are compiling on is running Mac OS (X) *without* forcing the user to tell us ... > 4. changed int vp [ 4 ] ; on line 202 of ssg.cxx to GLint vp [ 4 ] ; > 5. changed int ww; on line 112 of ssgLoadTexture.cxx to GLint ww; Why exactly was this neccessary ? PLIB passes normal int / float (whatever) variables or pointers to these types to the OpenGL routines expecting a GL* data type all the time (just look at PUI), and up to now, this has not caused any trouble as far as I can tell. If it does on Mac OS X, we have to change lots of lines (okay, in this case, 'sed' would be our friend ...). > Frameworks are Darwin's way of doing libraries, they are versioned > bundles (directories, actually) of headers,libraries and resources... > to link to a framework SOMEFW, you pass '-framework SOMEFW' to cc, and > to include header files out of it you include <SOMEFW/header.h>. > Frameworks are a nice idea... but a pain in the ass for porting stuff > from other unix platforms... Hmm ... who knows how to properly implement that stuff in our (up to now, pretty simple) autoconf-based build system ? - Sebastian |