From: Ilija Kocho <ilijak@siva.com.mk>
To: Michael Jones <mjones@linear.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Kinetis CYG_HAL_STARTUP_VAR conflict
Date: Sun, 02 Dec 2012 20:58:00 -0000 [thread overview]
Message-ID: <50BBC0F9.90101@siva.com.mk> (raw)
In-Reply-To: <FD403D8E-293F-4F44-A4DB-C17754002E70@linear.com>
On 02.12.2012 18:53, Michael Jones wrote:
> IIija,
>
> I would love to just use Eclipse, and have the Config tool generate a compatible tree. Then use a standard debugger interface, like the PEMicro tools. The experience using Code Warrior with MQX is overall good. The thing I don't like about MQX is having to configure things with #define in include files. I really like that eCos takes the configuration out of the code tree. This makes it much easier to have multiple configurations, especially when using source code control.
If you like scripting, also give a try to ecosconfig, great help for
repetitive jobs.
Ilija
--
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:[~2012-12-02 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 21:07 Michael Jones
2012-12-02 7:13 ` Michael Jones
2012-12-02 10:12 ` Ilija Kocho
2012-12-02 15:44 ` Michael Jones
2012-12-02 16:52 ` Ilija Kocho
2012-12-02 17:53 ` Michael Jones
2012-12-02 19:14 ` Ilija Kocho
2012-12-02 20:58 ` Ilija Kocho [this message]
2012-12-03 0:01 ` Michael Jones
2012-12-03 19:13 ` Ilija Kocho
2012-12-04 2:18 ` Michael Jones
2012-12-04 2:31 ` Michael Jones
2012-12-04 5:32 ` Michael Jones
2012-12-04 8:42 ` Ilija Kocho
2012-12-04 8:51 ` Ilija Kocho
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=50BBC0F9.90101@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=mjones@linear.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).