public inbox for
 help / color / mirror / Atom feed
From: Mo DeJong <>
To: sourcenav <>
Subject: Re: Fixing build bustage under VC++
Date: Thu, 21 Feb 2002 11:00:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, 21 Feb 2002 01:23:10 -0800
Ian Roxborough <> wrote:


> > I was under the impression that the tcl/cygwin directory was where
> > this "pure Cygwin" layer was going to live.

> Well, the apps being built think they are being built under UNIX
> and look in the ../unix location.
> A more correct solution would be to create a ../cygwin/
> and make all the apps currently using the ../unix/
> cygwin aware so they know to look in the ../cygwin directory.

Well, that should be a simple matter of adding some code to the
CYG_AC_PATH_TCLCONFIG macro defined in src/config/acinclude.m4.
Expect uses this macro so it should be a simple matter of updating
the m4 file and running autoconf in the expect dir. A tcl/cygwin/
already exists so that should not be a problem.

> What are your feelings on VC++ vs gcc for building SN?
> I'm left with the distinct impression building gcc
> would be easier, but then again, I'm just talk about
> compiling, I've yet to get it to run.

I think we should shoot for getting the VC++ build working again before
working on further gcc support under Windows. The main point of a
SN 5.1 release is to get the bug fixes and Tcl/Tk 8.3 upgrade out to
folks. I don't think that switching the release compiler at the same time
is such a good idea. Last I remember, the VC++ build was working
and SN was running (but, that was many moons ago). I seem to
remember that I had 90% of the packages compiling with mingw, but
there were a couple (perhaps Tix, db, or grep) that were not yet ported.
I know that at least Tcl, Tk, Incr Tcl,  and Incr Tk compiled with gcc.


  reply	other threads:[~2002-02-21  9:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 20:17 Mo DeJong
2002-02-20 21:13 ` Ian Roxborough
2002-02-21  0:08   ` Mo DeJong
2002-02-21  1:23     ` Ian Roxborough
2002-02-21 11:00       ` Mo DeJong [this message]
2002-02-21 12:06         ` Ian Roxborough
2002-02-20 23:14 ` Ian Roxborough

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).