From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11511 invoked by alias); 14 Mar 2006 18:44:51 -0000 Received: (qmail 11502 invoked by uid 22791); 14 Mar 2006 18:44:51 -0000 X-Spam-Check-By: sourceware.org Received: from mail.artimi.com (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 14 Mar 2006 18:44:49 +0000 Received: from rainbow ([192.168.1.165]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Mar 2006 18:44:47 +0000 From: "Dave Korn" To: Cc: "'Hermann-Simon Lichte'" , Subject: RE: how to link insight against 'external' TclTk frameworks on OSX Date: Tue, 14 Mar 2006 18:44:00 -0000 Message-ID: <000001c64797$5e3a4a30$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <44170ACD.7080508@gmail.com> Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00084.txt.bz2 On 14 March 2006 18:26, OpenMacNews wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > hi dave, > >>>> what must i do to ensure insight's use of *my* tcl/tk frameworks? >>> On http://sourceware.org/insight/faq.php it says: >>> >>> Right now, Insight MUST be built using the versions of Tcl, Tk, and >>> Itcl that come with the sources. We're working to fix that, but it is >>> going to take a lot of time. (Want to help?) >>> >> That's a red herring, > > damn subversive fish! ;-) If it wasn't for those damn subversive fish we'd all be squashed like sardines by the powers-that-be! Little known fact: Guy Fawkes was a fish.[*] >> as far as I'm aware it's very out-of-date info and >> 8.4.10 should work fine. >> >> The real question is where Richard has TCL_LIBRARY and TK_LIBRARY pointed >> at. See faq Q2.4. > > well, i agree, therein lies the challenge wrt the 'framework' builds on OSX. > > currently, i've: > > setenv TCL_LIBRARY "-F/Library/Frameworks -framework Tcl" > setenv TK_LIBRARY "-F/Library/Frameworks -framework Tk" > setenv TCL_INCLUDES "-I/Library/Frameworks/Tcl.framework/Headers" > setenv TK_INCLUDES "-I/Library/Frameworks/Tk.framework/Headers" > > which have been working for most other situations, but fail -- > apparently in insight's case -- to point to the right (i.e., mine) > tclConfig.sh etc etc It seems strange to me to have those flags and options in there, as far as I know both the T*_LIBRARY defines should be plain unardorned directory paths. I don't know for sure about the T*_INCLUDES defines. T*_LIBRARY are the necessary paths for the tcl/tk interpreters to find their files, and the flags are almost certainly wrong, but the XXX_INCLUDES defines are just part of configure trying to find the C header files for compiling code that interoperates with tcl/tk; in this case, adding some flags might make sense, much like defining CC='gcc -g -O2' does in other cases. But I don't know for sure. However before you run too much further down this thread wait for the other reply I was about to post to the other thread! cheers, DaveK [*] - Not true. -- Can't think of a witty .sigline today....