From: Emilio Monti <emilmont@gmail.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] JeCos
Date: Sun, 16 Oct 2005 14:44:00 -0000 [thread overview]
Message-ID: <68b1f7640510160744v2b4f099ex@mail.gmail.com> (raw)
When I use an open source software I like to give my contribute to it.
My interests are:
A Java configuration tool, possibly integrated in Eclipse.
A protocol to control an eCos embedded system via tcp/ip from a Java client.
For the first point, I have developed a parser for the eCos packages
database file.
The syntax of the database it's not so far from the one of the cdl
scripts, so it is a first small step.
For the second point, I have developed an eCos server and a Java
client with a Remote Procedure Call protocol.
All these softwares are released with a gpl license and are in an alpha version.
You can download the software at: http://sourceforge.net/projects/jecos
You can get more informations at: http://www.emilmont.net/?q=node/1
Any critique to the code it's welcome, any critique to its usefulness is not :-)
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2005-10-16 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68b1f7640510160744v2b4f099ex@mail.gmail.com \
--to=emilmont@gmail.com \
--cc=ecos-discuss@sources.redhat.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).