public inbox for
 help / color / mirror / Atom feed
From: "Pankaj Datta" <>
To: <>
Subject: Re: Cannot build project with windows binary
Date: Mon, 05 Nov 2001 08:31:00 -0000	[thread overview]
Message-ID: <004501c1746d$41a871a0$9b62f5d1@pancake> (raw)

Jordan, Syd, Ian, and others,
    I have run into the same problem that you are discussing in this =

>> C:\> PATH includes C:\SourceNavigator\H-i686-pc-
>> cygwin\bin;C:\cygwin;C:\cygwin\bin;

> Get rid of the semi-colons in the path.

I do not see how one could get rid of the semi-colons in a Windows/DOS =
path.  Syd could you explain?

>> confusing issue in all this is that "make" can be called by SN even
>> though it exists in the same directory as g++, rm, etc.

>Are you sure that you are running the correct make?
>(i.e. you might not be running the same one that is in the
> directory with g++, rm, etc.)

Ian, I do not see how one could choose which version of make they run, =
since if you use the default option (make) as the SN build command in =
the SN build dialog box,  SN seems to be using its own version of make.

Until someone corrects this problem here's a workaround.  Thought I'd =
share it with you and others who may be in the same situation.=20
My setup is:
    -- Windows 98 + SN5.0 + CYGWIN.
    -- SN is installed in C:\sn
    -- cygwin is installed in C:\cygwin
    -- Windows PATH var is set to =

1) Create a batch file, say C:\snmake.bat with the following:

    set =
    make %1 %2 %3 %4 %5

2) Use C:\snmake as your "Build command" in the SN build dialog box=20

The PATH command in the first line of the batch file allows you to =
display the kind of path SN  sees.   Incidentally, on my machine  doing =
2) causes the following output when PATH is executed:


As you can see from the above, SN seems to be using Unix style path spec =
for its own sub-path and appending it to the Windows path.  If you had =
the same path specification as above in a DOS comand shell, you would =
have no problem accessing rm , g++, or any other cygwin commands.   =
However, I think SN does some kind of parsing on the PATH and looses it! =
 Something for SN gurus to figure out.

The workaround I suggested above has a side-effect:  after the build is =
complete, you will have to press the  "Stop" button before you can do =
another build.

Hope this helps,


             reply	other threads:[~2001-11-23 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-05  8:31 Pankaj Datta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-05 14:25 Syd Polk
2001-10-17  3:37 Jordan
2001-10-17 10:16 ` Syd Polk
2001-10-17 11:42 ` 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 \
    --in-reply-to='004501c1746d$41a871a0$9b62f5d1@pancake' \ \ \

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