From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] eCos tools binary installation under Cygwin
Date: Tue, 29 Aug 2000 11:37:00 -0000 [thread overview]
Message-ID: <20000829133621.A4206@visi.com> (raw)
I've built and installed the ARM development tools under
NT4/Cygwin using the instructions at:
http://sources.redhat.com/ecos/tools/win-arm-elf.html
Assuming I've got a second computer running NT4 w/ the same
version of Cygwin, can I just copy the /tools directory to the
second computer, or do I need to copy the source/build
directories and do a "make install" on the second machine?
I don't use Windows much, and my past experience with copying
application program directory trees from one machine to another
hasn't been very successful. Under Win32, installing an app
seems to weave bits of the app deep into the system in
inextricable (and inexplicable) ways.
I'm hoping that stuff built/installed under Cygwin behaves in a
more Unix-like way... ;)
--
Grant Edwards
grante@visi.com
next reply other threads:[~2000-08-29 11:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-29 11:37 Grant Edwards [this message]
2000-08-29 11:57 ` Jonathan Larmour
2000-08-29 12:28 ` Ling Su
2000-08-29 12:43 ` Jonathan Larmour
[not found] ` <39AC12F4.9C2F7678@redhat.co.uk>
2000-08-29 17:18 ` [ECOS] eCos PCI problem and NEC vrc4373 build option Ling Su
2000-08-30 15:25 ` [ECOS] " Jonathan Larmour
2000-08-30 15:51 ` Ling Su
2000-08-30 15:58 ` Jonathan Larmour
2000-08-30 16:38 ` Alfredo Knecht
2000-08-30 17:20 ` Jonathan Larmour
2000-08-30 18:10 ` Alfredo Knecht
2000-08-30 18:22 ` Jonathan Larmour
2000-08-30 17:42 ` Ling Su
2000-08-30 18:02 ` Jonathan Larmour
2000-08-30 18:28 ` Ling Su
2000-08-30 18:57 ` Jonathan Larmour
2000-08-31 3:34 ` Nick Garnett
2000-08-31 10:57 ` Ling Su
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=20000829133621.A4206@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@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).