public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Peter Soetens <peter.soetens@mech.kuleuven.ac.be>
Cc: "Haibo Tang (QD/LJC)" <haibo.tang@ericsson.com>,
	"'ecos-discuss@sources.redhat.com'"
	<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] How to Make .epk. How to Make .ldi.
Date: Wed, 24 Sep 2003 18:10:00 -0000	[thread overview]
Message-ID: <20030924101529.B20997@visi.com> (raw)
In-Reply-To: <200309241315.27757.peter.soetens@mech.kuleuven.ac.be>; from peter.soetens@mech.kuleuven.ac.be on Wed, Sep 24, 2003 at 01:15:40PM +0200

On Wed, Sep 24, 2003 at 01:15:40PM +0200, Peter Soetens wrote:
> On Wednesday 24 September 2003 11:51, Haibo Tang (QD/LJC) wrote:
> > Hi,
> >
> > Is there any tool to make .epk ?  Is there any tool to generate .ldi ?
> 
> I have written a tool in Python 2.3 to generate .epk files. It is located on 
> my website :
> 
> http://people.mech.kuleuven.ac.be/~psoetens/ecos/ecospkggen.py

In case you don't have Python installed [you really should,
it's great!], I also posted to ecos-patches a similar though
much less featureful program written in bash. It's in the
mailing-list archive, or can be downloaded from
ftp://ftp.visi.com/users/grante/ecos/getpkg.sh Instructions for
use are in the mailing list archive.

-- 
Grant Edwards
grante@visi.com

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

  reply	other threads:[~2003-09-24 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24  9:52 Haibo Tang (QD/LJC)
2003-09-24 10:02 ` Jani Monoses
2003-09-24 11:15 ` Peter Soetens
2003-09-24 18:10   ` Grant Edwards [this message]
2003-09-24 18:27   ` [ECOS] how to get redboot.ram image Ramprasad

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=20030924101529.B20997@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=haibo.tang@ericsson.com \
    --cc=peter.soetens@mech.kuleuven.ac.be \
    /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).