From: Ian Roxborough <irox@redhat.com>
To: Bruce Edson <bruce@steptech.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Headaches building Source Navigator under Windows
Date: Thu, 21 Feb 2002 18:08:00 -0000 [thread overview]
Message-ID: <3C75B4D4.29F2D450@redhat.com> (raw)
In-Reply-To: <26F9F6EAB586D411850700B0D049E6E4014D2E3E@shasta.pdx.steptech.com>
Hi,
you need a full working Cygwin environment (which is kind
of like UNIX) to build Source-Navigators, the include
development tools like "make" (maybe in the usertools
and binutils packages?).
Don't know a great deal about Cygwin, but there is
a bunch of information over at:
http://www.cygwin.com/
I don't remember much about building on HP-UX, I'm
not sure if you'll need gcc or the HP-UX compiler.
Any HP-UX users got any tips?
Ian.
Bruce Edson wrote:
>
> Hi all,
>
> I've just been put on a project that requires creating a modified version of
> Source Navigator that runs under Windows 2000 and HP-UX. My first task is
> to get a buildable version working under Windows 2000. When I get tired of
> that, I get to do it again under HP-UX.
>
> Anyway, to my point, I've read a lot of docs, readmes and a lot of the
> emails regarding doing this under Windows. This is totally new to me so
> bare with me. I am familiar with VC++ 6.0 and that is what is installed on
> my Windows system. The directions in the Readme seem to take into account
> details that are not obvious to me. For instance, where do I put the Cygwin
> stuff in relation to the sources (it assumes I already have it), why doesn't
> the source tree come with make.exe, etc. The source I downloaded came from
> SN50-010322-source.zip.
>
> I've set up the environment with limited success creating the make file,
> when making my source directory a sub-directory of where the Cygwin.bat file
> is installed. I did see some errors, mainly couldn't find a certain file.
> But it made a makefile. However, the make doesn't run now because make.exe
> doesn't exist. Do I need to get that too? Where do I get one that is
> already built. What other issues am I going to run into?
>
> Long story short, is there a much more detailed, or canned approach
> available that I can follow step by step knowing I have a Windows system
> with just VC++6.0 loaded on it? One that includes everything that I need to
> download and what/how to configure? I'm not real familiar with the unix
> arena but am with the Windows. Any help would be greatly appreciated.
>
> The downloaded executable forms of SN work great on Windows, so I know it is
> buildable.
>
> Thanks in advance.
>
> Bruce Edson
next prev parent reply other threads:[~2002-02-22 1:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 17:47 Bruce Edson
2002-02-21 18:08 ` Ian Roxborough [this message]
2002-02-21 18:33 ` Mo DeJong
2002-02-21 18:35 ` Ian Roxborough
2002-02-22 13:21 Bruce Edson
2002-02-22 13:23 ` Syd Polk
2002-02-22 13:32 ` Ian Roxborough
2002-02-26 9:12 ` Mo DeJong
2002-02-26 9:20 ` Syd Polk
2002-02-27 8:32 ` Ralf Corsepius
2002-02-22 13:52 Bruce Edson
2002-02-22 14:48 ` Ian Roxborough
2002-02-26 0:23 Bruce Edson
2002-02-26 12:12 Bruce Edson
2002-02-26 12:30 Bruce Edson
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=3C75B4D4.29F2D450@redhat.com \
--to=irox@redhat.com \
--cc=bruce@steptech.com \
--cc=sourcenav@sources.redhat.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).