This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Building eCos.
- From: kalibar6 <kalibar6 at tlen dot pl>
- To: John Dallaway<john at dallaway dot org dot uk>, ecos-discuss at sourceware dot org
- Date: Fri, 04 Apr 2014 00:11:11 +0200
- Subject: Re: Building eCos.
- Authentication-results: sourceware.org; auth=none
- References: <8a84ec1 dot 20b7c9d1 dot 533c6a80 dot d62f8 at tlen dot pl> <533DA23D dot 9070105 at dallaway dot org dot 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