From: Jonathan Larmour <jlarmour@redhat.com>
To: mail_jeev@usa.net
Cc: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] [Fwd: ]
Date: Wed, 31 Jan 2001 23:23:00 -0000 [thread overview]
Message-ID: <3A790ED6.7FFE58B7@redhat.com> (raw)
In-Reply-To: <3A76BCA0.C202E1C4@redhat.com>
> From: ra jeev <mail_jeev@usa.net>
> hi guys,
> we are able to compile ecos successfully with our cross-compiler for
> an ARM target. where does the compiler store the image of ecos so that
> we can convert that image into binary and run it on our multiICE kit?
You link eCos directly with your application to give you the executable. I
recommend you read the Getting Started guide in the documentation to get
familiar with the principles.
> also when we compile our applications what will be the name of the
> executable, will it have a .axf extension?
No. GCC cannot generate ARM executable format binaries, although they are
very similar to the ELF format binaries GCC does generate. Someone may
already have written a conversion tool - I'd be interested to know if they
have.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-01-31 23:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 5:07 Jonathan Larmour
2001-01-31 23:23 ` Jonathan Larmour [this message]
[not found] <fc5cbb32050628021420c2a779@mail.gmail.com>
2005-06-28 11:27 ` [ECOS] Fwd: Rohit Agarwal
2005-06-28 11:51 ` Andrew Lunn
[not found] <rasyrb44.zus1w6nt.y50zz.hrkq@digitaldells.com>
2019-01-30 7:28 ` tayyaba azeem
[not found] <auqzdnwc.wdvvtvfr.7secq.5f1c@sammitrauto.com>
2020-02-17 18:57 ` tayyaba azeem
[not found] <dp5f9a4z.25wns5un.q3154.82ya@sammitrauto.com>
2020-02-17 18:57 ` tayyaba azeem
[not found] <eb5v1ts1.anctw1h5.50804.k6er@bbraunconnect.co.in>
2020-03-04 21:31 ` tayyaba azeem
[not found] <8xctmhsp.e9ez6v1u.153k3.crt7@bbraunconnect.co.in>
2020-03-04 21:31 ` tayyaba azeem
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=3A790ED6.7FFE58B7@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=mail_jeev@usa.net \
/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).