I'm now remembering that you discovered that we had to install the iPhone SDK to solve this. Is this included in Xcode 3.1?
Michael
On Sep 21, 2008, at 8:58 AM, <grass-user-request@lists.osgeo.org> wrote:
Date: Sun, 21 Sep 2008 10:58:27 -0500
From: William Kyngesburye <woklist@kyngchaos.com>
Subject: Re: [GRASS-user] Problems with OpenGL when compiling
grass-6.4.0 on Mac OS X 10.5.4
To: Elvis Dowson <elvis.dowson@mac.com>
Cc: grass-user@lists.osgeo.org
Message-ID: <91B049CD-7436-40E8-A90E-902DBCFB9C4D@kyngchaos.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yesOn Sep 21, 2008, at 1:23 AM, Elvis Dowson wrote:
Hi Michael,
Thanks for the reply.Could you please tell me what I should do to make it work with X11?
I am not
planning to use TclTk. I am planning to use vtk-5.2.0 and Qt-4.4.1.What I need to do is to link grass-6.4.0 or 7.0.0 with X11 and then
get it
to work inside vtk-5.2.0. I will then try to use the QVTK plug in to
create
a vtkRenderingContext using Qt.Just a note: the TclTk GUI may be dropped in GRASS 7.
So far, I have managed to get vtk-5.2.0 and qt-4.4.1 compiled and
running.I just have been stuck with getting any version of grass to compile
on Mac
OS X 10.5.4 using Xcode-3.1.1.Hmm, it should work without any patching.
X11 is broken on Leopard, it is impossible to compile programs
against it (more precisely whenever libGL is touched - directly or
indirectly). The easiest way to fix it is as follows:cd /usr/X11/lib
sudo bash
# enter your password
mv libGL.dylib libGL.dylib.apple
ln -s /System/Library/Frameworks/OpenGL.framework/Libraries/
libGL.dylib .This fixed the problem of ./configure being able to locate the
OpenGL libraries.I don't know where you came up with this - X11/OpenGL has always
worked (with the exception of the broken linker in Xcode 3.0 which is
fixed in 3.1).What is your configure command? Some things are supposed to be
automatically detected, but being explicit can help. See the macosx/
readme in the source for an example (much like Michael's configure).
Sometimes you may need to give the OpenGL or X11 configure options
some help.It's possible something is broken or misconfigured in your system. I
hate to ask, but do you have Fink or MacPorts installed? These add to
your shell PATH and may do other shell configurations that can
silently cause trouble.I have three copies of libGL.dylib. They are in the
following folders:
/usr/X11/lib
/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks/
OpenGL.framework/Versions/A/Libraries
/System/Library/Frameworks/OpenGL.framework/Libraries/LibrariesWhich is the correct one?
For X11, the X11 copy. The one in the SDK is just a duplicate of the
system framework, and will be used automatically if you use the -
isysroot flag. And in the end, X11 OpenGL gets much of its low-lewel
functionality from the system framework. With disabling the X11
OpenGL and symlinking the framework, as you did at the start, you lose
the X11-specific functions, like glX.So, I'd say you should restore the original X11 OpenGL library, then
figure out why configure can't find it. For configure errors, look in
config.log for more detail why a test failed.-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/"Those people who most want to rule people are, ipso-facto, those
least suited to do it."- A rule of the universe, from the HitchHiker's Guide to the Galaxy