From: Keith Seitz <keiths@redhat.com>
To: insight <insight@sourceware.org>
Subject: [PATCH/itcl] Update to Itcl 3.3
Date: Wed, 23 Jul 2008 22:48:00 -0000 [thread overview]
Message-ID: <4887B505.3080206@redhat.com> (raw)
Hi,
I've committed a mega-patch (omitted) to update the sourceware Itcl to
version 3.3. This is needed because Itcl 3.2 does not support TEA (Tcl
Extension Architecture), which we really need in order to use a
system-installed Tcl/Tk/Itcl/Itk/Iwidgets.
I have not tested it on Windows (Cygwin or Mingw) yet, so there may be
problems... I'll try to check these sometime soon.
Keith
2008-07-23 Keith Seitz <keiths@redhat.com>
Import of Itcl 3.3.
* itcl/configure.in, itk/configure.in, iwidgets/configure.in:
Replace with configure.ac.
* itcl/configure, itk/configure, iwidgets/configure: Regenerate.
* configure.ac, Makefile.am, Makefile.in: New files.
* README: "New" file.
* aclocal.m4: Regenerate.
* itcl/Makefile.in (RANLIB): Replace with RANLIB_LIB so
that the toplevel build does not override this variable.
* itk/Makefile.in (RANLIB): Likewise.
* itcl/tclconfig/tcl.m4 (TEA_PATH_TCLCONFIG): Look for
itclConfig.sh
in the platform-specific location (unix or win).
(TEA_PATH_TKCONFIG): Likewise.
(TEA_MAKE_LIB): Even on windows, GCC libraries must start with
"lib".
* itk/tclconfig.m4: Copy of itcl/tcl.m4.
* iwidgets/tcl.m4: Remove.
* iwidgets/tclconfig: New directory.
* iwidgets/tclconfig/tcl.m4, iwidgets/tclconfig/install-sh: Copies
of itcl/tclconfig files.
* iwidgets/Makefile.in (MKINSTALLDIRS): Use mkdir -p.
* iwidgets/configure.ac (PACKAGE): Rename to PACKAGE_NAME.
Call TEA_INIT, add AC_CONFIG_AUX_DIR and AC_PROG_INSTALL.
Use TEA_* instead of SC_* macros.
Search a few more directories for the itcl and itk libraries.
next reply other threads:[~2008-07-23 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 22:48 Keith Seitz [this message]
2008-08-01 22:48 ` Tom Tromey
2008-08-02 0:31 ` Keith Seitz
2008-08-02 3:34 ` Tom Tromey
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=4887B505.3080206@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).