From: Chris Gehlker <gehlker@...>
Date: 2002-03-22T04:01:39+09:00
Subject: Mkmf on MacOSX was: Ruby/Tk on OSX

Somebody, maybe Massimiliano, was asking about mkmf on Mac OSX. Having
hacked a little on the problem with Tk/Tcl, I now have some insight.
Sometimes headers are stored in a directory named 'include' but this is only
for stuff that the Darwin folks envisioned as necessary for basic
compatibility. Often headers are in a directory named 'Headers' in some
subdirectory of /System/Library/Frameworks.

Mkmf#with-name-include wont find such headers because the 'include' is hard
coded.

I can think of two solutions:
1) Hack mkmf#with-name-include to accept 'Headers'.
2) Add a with-name-headers method to mkmf.

I prefer the latter. I'm not sure why, but the fact that the former is not a
complete solution, has something to do with it. Extconf.rb files still need
to be customized for the Mac to add /System/Library/Frameworks/xxx to the
search path.

I'm by no means sure that this is the whole problem.

When and if I work this mess out what do I do to change the standard Ruby
distribution? Is that what RCRs are for?
--
In the midst of great joy, do not promise anyone anything. In the midst of
great anger, do not answer anyone's letter. -Chinese proverb