From: Ian Roxborough <irox@redhat.com>
To: Mo DeJong <supermo@bayarea.net>
Cc: sourcenav <sourcenav@sources.redhat.com>
Subject: Re: Fixing build bustage under VC++
Date: Wed, 20 Feb 2002 23:14:00 -0000 [thread overview]
Message-ID: <3C749373.A917C13A@redhat.com> (raw)
In-Reply-To: <20020220175911.48e153f5.supermo@bayarea.net>
Mo DeJong wrote:
>
> Hi all.
>
> I took a quick look at why sourcenav fails to build under VC++ these days.
Cool.
I built Source-Navigator with gcc/cygwin today,
there wheren't too many changes to do, I was pretty
impressed that it built, how ever it didn't run
and I didn't have time to look why it was crashing
on start up.
I'd prefer to make gcc the default compiler for
Windows, because VC++ costs money and it'll be
easier to support since it's closer to the UNIX
version.
I've going to look into it again, maybe it's not
going to take too much to fix.
Ian.
prev parent reply other threads:[~2002-02-21 5:13 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
2002-02-21 12:06 ` Ian Roxborough
2002-02-20 23:14 ` Ian Roxborough [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=3C749373.A917C13A@redhat.com \
--to=irox@redhat.com \
--cc=sourcenav@sources.redhat.com \
--cc=supermo@bayarea.net \
/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).