public inbox for
 help / color / mirror / Atom feed
From: Jordan <>
Subject: Cannot build project with windows binary
Date: Wed, 17 Oct 2001 03:37:00 -0000	[thread overview]
Message-ID: <15355.20919.39040.782297@pride.nsw.cmis.CSIRO.AU> (raw)


This is another request for assistance regarding my attempts to build
some simple projects inside the windows release of SN 5.0.

Thanks to Syd, Bernard and Khamis for their comments so
far. Unfortunately, no dice.

My setup:

Windows 2000
Cygwin is located at C:\cygwin
SourceNavigator is located at C:\SourceNavigator

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

I can build the "projects" from the command line in both a Windows
Command prompt window and from a cygwin bash shell proving that in
both cases, gcc is in the search path.

Results from SN:

Clean build of room.proj

rm -f *.o
rm -f libclassroom.a
make: rm: Command not found
make: *** [clean] Error 127
+++ End +++

Build of head.proj

g++ -c main.cpp   
make: g++: Command not found
make: *** [main.o] Error 127
+++ End +++

I can set up these projects in version of SourceNavigator I built from
source on my linux box and the projects build and run OK, proving that
it is not my project build setup inside SN that is the problem.  The
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.

So either my Cygwin/Sn setup is skewif on the windows side or the
windows binary hasn't been built properly as it can't locate the tools
with which to build the projects.

I would ideally like somebody to do a fresh install of the SN 5.0
binary to identify if my experience is actually a bug.
Any inspiration divine or otherwise gratefully accepted.


P.S. As before please Cc me directly when replying to the list, thanks.

             reply	other threads:[~2001-11-21  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-17  3:37 Jordan [this message]
2001-10-17 10:16 ` Syd Polk
2001-10-17 11:42 ` Ian Roxborough
2001-11-05  8:31 Pankaj Datta
2001-11-05 14:25 Syd Polk

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=15355.20919.39040.782297@pride.nsw.cmis.CSIRO.AU \ \ \

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