From: kalibar6 <kalibar6@tlen.pl>
To: "John Dallaway" <john@dallaway.org.uk>, ecos-discuss@sourceware.org
Subject: [ECOS] Re: Building eCos.
Date: Thu, 03 Apr 2014 22:11:00 -0000 [thread overview]
Message-ID: <78dd7233.15f8eb99.533ddc7f.8013f@tlen.pl> (raw)
In-Reply-To: <533DA23D.9070105@dallaway.org.uk>
Wow! That was so easy and solved the problem. I still do not know why I could not compile the whole thing but it does not matter anymore.
Thanks John.
Dnia 3 kwietnia 2014 20:02 John Dallaway <john@dallaway.org.uk> napisał(a):
> Hi
>
> Since you are new to eCos, I would suggest downloading the latest
> snapshot build of the eCos Configuration Tool for Linux hosts. Ref:
>
> http://ecos.sourceware.org/ml/ecos-discuss/2011-02/msg00031.html
>
> You might also download the arm-eabi test release toolchain. Ref:
>
> https://www.sourceware.org/ml/ecos-discuss/2012-06/msg00047.html
>
> In the eCos Configuration Tool, set the eCos repository location (Build
> >> Repository) as follows:
>
> /home/kalbar/CVS_repo/ecos_host
>
> (this is the folder containing the "packages" folder)
>
> You should then see the eCos configuration tree.
>
> Select the STM32F4-Discovery hardware template (Build >> Templates).
>
> Select the location of your arm-eabi toolchain "bin" folder containing
> arm-eabi-gcc (Tools >> Paths >> Build Tools).
>
> You should then be able to build eCos.
>
> I hope this helps...
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2014-04-03 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 19:52 [ECOS] " kalibar6
2014-04-03 10:11 ` AW: " Richard Rauch
2014-04-03 18:02 ` [ECOS] " John Dallaway
2014-04-03 22:11 ` kalibar6 [this message]
[not found] <200003011701.JAA18830@cygnus.com>
2000-03-03 6:49 ` 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=78dd7233.15f8eb99.533ddc7f.8013f@tlen.pl \
--to=kalibar6@tlen.pl \
--cc=ecos-discuss@sourceware.org \
--cc=john@dallaway.org.uk \
/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).