From: "Mills, John" <john.mills@atl.viasat.com>
To: "'Breckner.Robert.E'" <Robert.Breckner@IGT.com>,
"'sourcenav@sources.redhat.com'" <sourcenav@sources.redhat.com>
Subject: RE: Newbie questions
Date: Fri, 01 Jun 2001 12:30:00 -0000 [thread overview]
Message-ID: <5C44CEE7DF7AD4119783000629A813F0096894@SRV32-EXCH-NTS> (raw)
Hello -
I used SN-4.2 in Linux for cross development; since I had a Makefile, the
build took its instructions from that file and created whatever targets were
specified there, as well as running the specified cross-toolset.
I did a limited amount of work also with SN-4.2 in WinNT. The GNU tools
themselves were hosted under 'cygwin', and I started SN from a cygwin
console for them to inherit that environment. (There may be a _much_ more
direct approach I didn't find, but that worked.)
Could you take that approach?
DISCLAIMERS - I haven't put much use on 5.0, I never used the SN building
tools, nor am I doing cross-platform development at the moment.
Regards
- John Mills
-----Original Message-----
From: Breckner.Robert.E [ mailto:Robert.Breckner@IGT.com ]
Sent: Wednesday, May 30, 2001 7:54 PM
To: 'sourcenav@sources.redhat.com'
Subject: Newbie questions
I would really like to use Source Navigator as a cross development
environment for a platform that has the 2.95.2 gnu toolset already available
for Windows 2000. In general I found that everything worked great except
for a few items.
next reply other threads:[~2001-06-01 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 12:30 Mills, John [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-01 13:34 Breckner.Robert.E
2001-05-30 16:54 Breckner.Robert.E
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=5C44CEE7DF7AD4119783000629A813F0096894@SRV32-EXCH-NTS \
--to=john.mills@atl.viasat.com \
--cc=Robert.Breckner@IGT.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).