From: Bart Veer <bartv@redhat.com>
To: JDabbs@TGA.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] eCos with non-GNU compiler
Date: Wed, 13 Sep 2000 10:13:00 -0000 [thread overview]
Message-ID: <200009131713.SAA03927@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <487BF2740AEBD311831F006008AE0B6E0BF7BC@NS1>
>>>>> "James" == James Dabbs <JDabbs@TGA.com> writes:
James> Pardon any naivety..
James> Has anyone build eCos with compilers other than GNU? For
James> instance, Diab or Green Hills? If so, how did it go?
James> Also, is anyone developing eCos targets from a Windows
James> host? What were your experiences in this area?
James> The real question (internally here) is whether eCos is tied
James> to Linux/GNU/GDB, or if anyone has used MULTI or any other
James> windows cross-IDE to build eCos projects.
eCos has a number of dependencies on the GNU compilers, see
http://sources.redhat.com/ecos/faq.html#porting_compiler
It may be possible to use debuggers other than gdb, provided they can
cope with the output of the GNU compilers and linker. If the debugging
is intrusive, i.e. you need to run some sort of debug stub on the
target in addition to the application, then you would have to
integrate this stub into the system somehow. The current system comes
only with a gdb stub because the core developers use gdb.
eCos development is not tied to a Linux host, in fact one of the tools
(the graphical configuration tool) is currently only available for
Windows hosts. The installation instructions at
http://sources.redhat.com/ecos/getstart.html provide information for
both Linux and Windows hosts.
I am afraid I do not know anything about MULTI, e.g. whether or not it
allows the compiler to be selected.
Bart Veer // eCos net maintainer
next prev parent reply other threads:[~2000-09-13 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-13 9:43 James Dabbs
2000-09-13 10:13 ` Bart Veer [this message]
2000-09-13 14:04 ` [ECOS] eCos with non-GNU tools Greg Shubin
2000-09-13 14:57 ` Jonathan Larmour
2000-09-13 15:08 ` Matthew H. Gerlach
2000-09-14 5:41 ` Bart Veer
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=200009131713.SAA03927@sheesh.cygnus.co.uk \
--to=bartv@redhat.com \
--cc=JDabbs@TGA.com \
--cc=ecos-discuss@sourceware.cygnus.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).