public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Jonathan Larmour <jlarmour@redhat.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Build eCos under Windows and Linux w/ same source tree?
Date: Thu, 31 Aug 2000 10:26:00 -0000	[thread overview]
Message-ID: <20000831122624.A16095@visi.com> (raw)
In-Reply-To: <39AE9366.EDE23083@redhat.com>

On Thu, Aug 31, 2000 at 06:18:30PM +0100, Jonathan Larmour wrote:

> Firstly, you can change the destination directory. But since
> installing the source tree isn't what you want anyway, you
> could cheat - get the ecosconfig.exe tool from
> http://sources.redhat.com/ecos/anoncvs.html under the bit about
> updated host tools.

Ah. I should have though of that. It didn't occur to me that
there would be executables in the CVS repository.

> >I'd like to be able to build eCos under Windows using the same
> >source tree I build from under Linux.
> 
> Make sure you use the "Linux" version of the tree, i.e. without
> CRLF endings. Otherwise you may get problems on Linux with CRs
> at the end of lines such as preprocessor continuation chars,
> e.g.
> 
> #if defined(foo) || \
>     defined(bar)

Thanks for the tip.  I just finished building eCos under
Windows by doing the "ecosconfig tree" under Linux and copying
the build-tree over to Windows and doing a "make".

Once I copied /bin/bash.exe to /bin/sh.exe everything was
peachy-keen.

-- 
Grant Edwards
grante@visi.com

      reply	other threads:[~2000-08-31 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-31  8:55 Grant Edwards
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 [this message]

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=20000831122624.A16095@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@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).