public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Build eCos under Windows and Linux w/ same source tree?
Date: Thu, 31 Aug 2000 08:55:00 -0000	[thread overview]
Message-ID: <20000831105518.A2120@visi.com> (raw)

I'd like to be able to build eCos under Windows using the
same source tree I build from under Linux.

I've been able to build and run eCos applications under Windows using an
eCos kernel built under Linux, so I'm pretty sure Cygwin and the Gnu cross
tools are all working -- next I'd like to try building eCos under Windows.

So far I've figured out that I need a Win32 version of "ecosconfig".  For
now I'd like to stick with command-line tool, since I've made changes to the
HAL memory-map files that would be over-written by the GUI tool.

Should this work?

-- 
Grant Edwards
grante@visi.com

             reply	other threads:[~2000-08-31  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-31  8:55 Grant Edwards [this message]
2000-08-31  9:52 ` Grant Edwards
2000-08-31 10:12   ` Ling Su
2000-08-31 10:18   ` Jonathan Larmour
2000-08-31 10:26     ` Grant Edwards

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=20000831105518.A2120@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).