Re: [MACTCL] Tcl/Tk compilation on Yosemite - what's the point of requiring X sans X?

[<l....@su...>]

http://savi.sf.net uses no Tk extensions, to my knowledge; just Tk itself. Extensions would decrease crossplatform portability, which I view as important. SaVi predates Mac OS X...

Having to install Xcode AND XQuartz is not entirely desirable, but more so than trying to build and maintain a Mac-only binary.

Trying to set up a Tk development environment for unix from scratch on a pristine Mac OS sans Xcode might be a useful exercise to do for Tk developers to gain insight into the barriers to starting with tk. We're cushioned by our environments.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Kevin Walzer <kw...@co...>
Sent: Monday, 1 December 2014 2:06:08 PM
To: Wood L  Dr (Electronic Eng); tc...@li...
Subject: Re: [MACTCL] Tcl/Tk compilation on Yosemite - what's the point of requiring X sans X?

On 11/30/14, 8:15 AM, l....@su... wrote:
> So, recommending Mac users install XQuartz (and ActiveTcl?), to reduce reliance on what ships with Mac OS X, would be the simplest way to go? (10.9 has Tcl/Tk 8.5.9, which is better than previous. Not sure about 10.10. ActiveTcl is probably still ahead.)

I've run into a similar issue with the X11 headers in trying to install
a Tk extension (not Tk itself, it can find its own headers)--perhaps
that is what Lloyd is seeing. I also fixed the issue by installing
XQuartz and adding it to my path so that it found the headers. I have no
idea why this problem arises, but I think it makes sense as a best
practice to install XQuartz when building Tk extensions.

--Kevin

--
Kevin Walzer
Code by Kevin/Mobile Code by Kevin
http://www.codebykevin.com
http://www.wtmobilesoftware.com