From: John Dallaway <john@dallaway.org.uk>
To: kalibar6 <kalibar6@tlen.pl>
Cc: eCos Discussion <ecos-discuss@sourceware.org>
Subject: [ECOS] Re: Building eCos.
Date: Thu, 03 Apr 2014 18:02:00 -0000 [thread overview]
Message-ID: <533DA23D.9070105@dallaway.org.uk> (raw)
In-Reply-To: <8a84ec1.20b7c9d1.533c6a80.d62f8@tlen.pl>
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
-------- Original Message --------
Subject: Building eCos.
Date: Wed, 02 Apr 2014 21:52:32 +0200
From: kalibar6 <kalibar6@tlen.pl>
To: ecos-discuss@ecos.sourceware.org
Newsgroups: gmane.os.ecos.general
Hi all,
I am trying to play a bit with eCos on STM32F4 Discovery board. I am
working under Ubuntu 12.04 (32bit). I know that in downloaded binaries
there is no support for this platform. I have to download source files from
CVS repository and compile them myself. OK. I have downloaded them:
cvs -z3 -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -P ecos
cvs -z3 -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -P host
System variable $ECOS_REPOSITORY has been set up to my downloaded files:
/home/kalbar/CVS_repo/ecos_host/packages
Now after multiple approaches I can't get this thing fully compiled and
installed. In main source folder I have created folder 'build' and run
configure script and make and install:
/home/kalbar/CVS_repo/ecos_host/configure
--prefix=/home/kalbar/CVS_repo/ecos_host/build --with-tcl=/usr/lib/tcl8.4
--with-tk=/usr/lib/tk8.4
make
sudo make install
Some files are getting compiled/build but not all of them. There is still
lack of GUI for eCos configuration and package for for my board does not
seem to build. I would really appreciate some help on this matter as I have
spend quite a lot of time on this and got stuck in dead end with no help
from README files nor google.
--
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 18:02 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 ` John Dallaway [this message]
2014-04-03 22:11 ` [ECOS] " kalibar6
[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=533DA23D.9070105@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-discuss@sourceware.org \
--cc=kalibar6@tlen.pl \
/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).