public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Lars Poeschel <larsi@wh2.tu-dresden.de>
To: ecos-devel@ecos.sourceware.org
Subject: Re: configtool development
Date: Mon, 03 Jul 2006 09:38:00 -0000	[thread overview]
Message-ID: <50a2a726f04bce28055ee903d72d814c@wh2.tu-dresden.de> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello!
Last week I announced a patch for the host tools and configtool on 
ecos-patches, but there was no reaction. It is possible that there is 
currently no maintainer for this ?
I send the mail here again in hope someone responsible gets noticed. 
See below.

So long,

Lars Poeschel

> Hello!
>
> As i announced on ecos-devel I worked on the configtool. As a result I 
> created the following patch. I worked on Linux and tried to be as 
> Windows friendly as possible, but I could not test if it workes with 
> Windows.
> The patch does not include the patch of Andy Jackson from xylanta and 
> should not conflict with it.
> It moves complete host-tools (including configtool) to recent autoconf 
> / automake. It also makes configtool use the recent wxWidgets library 
> of the installed distribution. No seperate built and installed 
> wxWidgets is needed. 2.6.x wxWidgets should also work. Most modern 
> distributions install an unicode version of wxWidgets. Configtool is 
> changed to be able to work with unicode libraries.
> After applying the patch to cvs ecos-host, configure scripts and 
> Makefiles have to be built by executing autoreconf in the host 
> directory. After that, everything is ready to be configure'd and 
> make'd in a seperate build directory as documented on the website.
> For most distributions you have to supply the tcl version to configure 
> using the --with-tcl=8.4 option for example.
> I hope this patch is useful for you. You can get it here:
>
> http://www.mr.inf.tu-dresden.de/eCos/ct060628.patch.gz
>
>
> Greetings,
>
> Lars Poeschel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEqOVz3m3cZ1XsbwcRAivHAJ9UxFVOXdOUUkLyQkQJ9HiAKfUZ1QCfUYhe
94YsxoJ4O/mHLETR8N5lLrY=
=U5by
-----END PGP SIGNATURE-----

             reply	other threads:[~2006-07-03  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03  9:38 Lars Poeschel [this message]
2006-07-03 10:18 ` John Dallaway
  -- strict thread matches above, loose matches on Subject: below --
2006-04-14 17:47 Lars Poeschel
2006-04-14 17:59 ` Jiri Gaisler
2006-04-14 19:20 ` Fabian Scheler
2006-05-01 14:21 ` Andy Jackson
2006-05-01 16:15   ` Andrew Lunn
2006-05-02  8:57   ` John Dallaway
2006-06-01 17:38     ` Fabian Scheler
2006-06-01 15:50       ` John Dallaway

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=50a2a726f04bce28055ee903d72d814c@wh2.tu-dresden.de \
    --to=larsi@wh2.tu-dresden.de \
    --cc=ecos-devel@ecos.sourceware.org \
    /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).