Re: [M-dev]Problems building OSX/Carbon

[<br...@ma...>]

Doesn't really help in this case. For Mac OS X the SDL files are all 
embedded in frameworks. Our PB Project actually has added search paths 
for things like ${HOME}/SDL_net.framework/Headers to solve the problem. 
Annoying, but it works. And not sure of a way around that otherwise 
because Frameworks, not raw libraries are the Mac OS X Way (tm) to do 
them.

With regards to the SDL libraries themselves, I'm wondering if the 
inability to use them as a private shared library without a recompile is 
a bug or not that should be submitted to the maintainers of the Mac OS X 
version. (The default embedded search path in the framework has the same 
problem that we had fighting to avoid absolute paths in our pbproj file 
itself.)

---------------------+------------------------------------------------------
Br'fin               |      TIMSter, MU*er, Web Programmer, ... Insane?
The Denim Warrior    |                  You be the judge...
br...@ma...       |          http://www.concentric.net/~brefin/
---------------------+------------------------------------------------------

On Saturday, August 10, 2002, at 04:57  PM, Woody Zenfell wrote:

> Observe that SDL headers should generally be #include "sdl_blah.h" 
> rather
> than #include <sdl_blah.h> or #include <sdl/sdl_blah.h>.  This way the
> (platform-specific) project file's search paths can take care of the
> platform-specific locations of things, and the code itself does not 
> have to
> have different paths for different platforms.  Yeah sort of defeats the
> purpose of distinguishing "" from <>, but it effectively works around 
> this
> problem, and is the official recommendation from the SDL folks (see the 
> SDL
> development FAQ).
>
> I think.  :)
>
> Woody
>