public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Mike D" <mike@clockwork.freeserve.co.uk>
To: <sourcenav@sourceware.cygnus.com>
Subject: Re: Building Source navigator on Windows
Date: Sun, 23 Jul 2000 23:23:00 -0000	[thread overview]
Message-ID: <005e01bff537$9c7d5890$076f883e@Workgroup> (raw)
In-Reply-To: <3978C168.557DC197@cygnus.com>

>
> > To build Source Navigatot under Windows currently requires both Cygwin
and
> > the Microsoft Visual C++ compiler.
>
> Right now we have only tried it with Visual C++ 5.0. 6.0 has its own
> issues and problems. Rather than fix them, we are working on building
> with cygwin in our current development. Probably won't be real for a few
> months.

I will have to fix them then,  I only have VC++ 6.0,  not 5.0.  Do you have
a list of known or anticipated problems ?  The only thing that is
immediately obvious is that the initial project file add stage only seems to
indicate progress when the mouse pointer is held over the progress box.

> > 6 (strange but true) set some environment variables that make the build
use
> > the VC++ compiler instead of the cygwin one :  <export CC=cl>  <export
> > CFLAGS="-Z7 -Od">
>
> Actually, I will post the real CFLAGS that I use when I get back to
> work.

OK, thanks.

> >
> > 10 build Source Navigator  <make>
>
> Use "make all-snavigator".

I tried this,  but the executables seem to be the same as I got when I did
make by itself.  On the other hand <make install-snavigator>  didn't
recurse,  so that's one advantage :-)

>>it would be nice to know that
> > any bugs are due to my changes,  not my build methodology
>
> Without build logs, it is hard to tell.

Could you post me a build log from your system ?   I want to try to use
Source Navigator as a replacement for a build system we use at work (based
on an old version of Polymake).  I am going to have to make some mods to
alow SN to read our current file build instruction and it would be really
useful to know that the base build was the same.


Thanks,

Mike.


      reply	other threads:[~2000-07-23 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-21  4:09 Thomas Heller
2000-07-21 14:13 ` Mike D
2000-07-21 14:32   ` Syd Polk
2000-07-23 23:23     ` Mike D [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='005e01bff537$9c7d5890$076f883e@Workgroup' \
    --to=mike@clockwork.freeserve.co.uk \
    --cc=sourcenav@sourceware.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).