From: Keith Seitz <keiths@redhat.com>
To: insight@sourceware.org
Subject: Re: how to link insight against 'external' TclTk frameworks on OSX
Date: Tue, 14 Mar 2006 19:12:00 -0000 [thread overview]
Message-ID: <44171586.3080001@redhat.com> (raw)
In-Reply-To: <AAE106C6-101C-48E2-A03F-2290FA52A696@gmail.com>
Hermann-Simon Lichte wrote:
> Hello Richard,
>
>> 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?)
Okay, well that's mostly true. For example, I just replaced the versions
of tcl and tk that come with Insight with the latest stable release from
ActiveState. Add the configure.in and Makefile.in from the
sourceware.org versions, and poof! Insight built with tcl/tk 8.4.12.
Now, as for using an external insight, the FAQ is correct. There is no
way to do this just yet. It's going to require a bunch of autoconf
hacking, and it could get tricky, since CVS will *always* have a copy
Tcl around (for dejagnu).
I just haven't had either the time or the motivation to embark on this.
I'm just not sure it's worth it: insight is on its last legs, as it were.
Keith
next prev parent reply other threads:[~2006-03-14 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 7:29 OpenMacNews
2006-03-14 8:30 ` Hermann-Simon Lichte
2006-03-14 8:37 ` OpenMacNews
2006-03-14 9:09 ` Hermann-Simon Lichte
2006-03-14 18:17 ` Dave Korn
2006-03-14 18:26 ` OpenMacNews
2006-03-14 18:44 ` Dave Korn
2006-03-14 19:14 ` Keith Seitz
2006-03-14 19:12 ` Keith Seitz [this message]
2006-03-14 20:09 ` OpenMacNews
2006-03-14 20:51 ` Keith Seitz
2006-03-14 23:00 ` OpenMacNews
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44171586.3080001@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).