public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Mikhail Teterin <mi+kde@aldan.algebra.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org
Subject: Re: Questioning the withdom of bundling gdb and insight
Date: Fri, 29 Jun 2007 00:56:00 -0000	[thread overview]
Message-ID: <200706282055.59304@aldan> (raw)
In-Reply-To: <446B32E2.3080107@redhat.com>

On ц⌠ц┘ц▓ц┘ц└ц│ 17 ц■ц▓ц│ц≈ц┘ц▌ц≤ 2006, Keith Seitz wrote:
= PS. Patches welcome to build using external tcl, tk, itcl...

The patch for the itcl code, to make it work with ITcl/ITk-3.3 can be found 
here:

http://www.freebsd.org/cgi/cvsweb.cgi/ports/devel/gdb6/files/itcl33-patch?rev=HEAD;content-type=text%2Fplain

FreeBSD port of gdb can now be (optionally) built with Insight. If the 
GUI-option is enabled, the following additional flags are passed to gdb's 
configure:

	--enable-gdbtk  --with-tclconfig=/usr/local/lib/tcl8.4	\
	--with-tclinclude=/usr/local/include/tcl8.4/generic	\
	--with-tkconfig=/usr/local/lib/tk8.4	\
	--with-tkinclude=/usr/local/include/tk8.4/generic	\
	--with-itclconfig=/usr/local/lib/itcl3.3	\
	--with-itkconfig=/usr/local/lib/itk3.3

Note, that the obsolete version of itcl (and itk) bundled with insight is not 
extracted. Instead, headers of ITcl and ITk 3.3 headers are sym-linked into 
the (otherwise empty) itcl/generic subdirectory.

To spare the FreeBSD users the need to download the entire insight (22Mb), I 
rolled my own tarball, which contains _only_ the gdb/gdbtk and the libgui 
subdirectories of the distribution (845Kb):

	http://aldan.algebra.com/~mi/gdbtk-6.6.tar.bz2

This is extracted on top of the gdb-6.6 sources, if the user asks for the GUI 
option.

Please, consider upgrading your GUI code to ITcl/ITk-3.3 using the patch 
provided.

Please, independently consider abandoning the practice of bundling 
ITcl/IWidgets with Insight.

Please, independently consider releasing the Insight's _extra code_ in 
_addition_ to the gdb tarball, instead of bundling gdb sources inside 
Insight's.

Thank you,

	-mi

      parent reply	other threads:[~2007-06-29  0:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17  2:02 Mikhail Teterin
2006-05-17 14:31 ` Keith Seitz
2006-05-17 17:50   ` Mikhail Teterin
2006-05-17 17:57     ` Dave Korn
     [not found]   ` <200605171330.50762.mi+mx@aldan.algebra.com>
2006-05-17 17:53     ` Does insight work? Keith Seitz
2006-05-17 18:06       ` Mikhail Teterin
2006-05-17 18:08         ` Keith Seitz
2006-05-17 18:15           ` Mikhail Teterin
2006-05-17 18:27             ` Keith Seitz
2006-05-17 18:41               ` Mikhail Teterin
2006-05-17 19:03               ` Single-executable patch Mikhail Teterin
2006-05-17 19:07                 ` Daniel Jacobowitz
2006-05-17 19:28                   ` Mikhail Teterin
2006-05-17 19:35                     ` Daniel Jacobowitz
2006-05-17 20:32                 ` Eli Zaretskii
     [not found]   ` <200605171337.30938.mi+mx@aldan.algebra.com>
2006-05-17 17:55     ` Questioning the withdom of bundling gdb and insight Keith Seitz
2006-05-17 18:11       ` Mikhail Teterin
2006-05-17 18:20         ` Keith Seitz
2006-05-17 18:31           ` Mikhail Teterin
2007-06-29  0:56   ` Mikhail Teterin [this message]

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=200706282055.59304@aldan \
    --to=mi+kde@aldan.algebra.com \
    --cc=insight@sourceware.org \
    --cc=keiths@redhat.com \
    /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).