public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Jim Ingham <jingham@apple.com>
To: Tom Tromey <tromey@cygnus.com>
Cc: Cor van Loos <C_van_Loos@excite.com>, <Insight@sourceware.cygnus.com>
Subject: Re: Building Insight (2)
Date: Thu, 29 Jun 2000 18:00:00 -0000	[thread overview]
Message-ID: <B5813F34.1EDA%jingham@apple.com> (raw)
In-Reply-To: <200006300037.RAA29272@ferrule.cygnus.com>

Also sprach Tom Tromey:

> Jim> P.S. I also agree with Keith that libgui should NOT be trying to
> Jim> make the tclIndex as part of the build.  It is too fragile,
> Jim> particularly since the wrong version of Itclsh can cause really
> Jim> bad things to happen...
> 
> One approach to this, which is both controversial and widely
> practiced, is to check in the derived file and make rebuilding it
> conditional upon configuring with --enable-maintainer-mode.
> This is easiest if you're using automake, but it is also fairly easy
> without it.
> 
> Tom

That is what I tend to do - but in a sloppy sort of way...  In Insight we
just have a tclIndex target, which no other target depends on.  Then I just
remember that if I change any of the Tcl files, I need to run it.  This
depends on the developer being disciplined, but rebuilding the index with
every build is more not right, since the vast majority of the people who
build Insight are NOT messing with the libgui tcl files, and so for them to
build the index just adds an element of risk with no real benefit.

Jim
-- 
Jim Ingham                                 jingham@apple.com
Apple Computer

  reply	other threads:[~2000-06-29 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-29  4:52 Cor van Loos
2000-06-29  5:13 ` Mo DeJong
2000-06-29  5:45 ` Keith Seitz
2000-06-29 15:47 ` Kai Ruottu
2000-06-29 17:24 ` Jim Ingham
2000-06-29 17:34   ` Syd Polk
2000-06-29 17:37   ` Tom Tromey
2000-06-29 18:00     ` Jim Ingham [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28  0:21 Cor van Loos
2000-06-28  9:13 ` Syd Polk
2000-06-23  5:35 Cor van Loos
2000-06-23  5:57 ` Mo DeJong

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=B5813F34.1EDA%jingham@apple.com \
    --to=jingham@apple.com \
    --cc=C_van_Loos@excite.com \
    --cc=Insight@sourceware.cygnus.com \
    --cc=tromey@cygnus.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).