public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <jld@ecoscentric.com>
To: Emmet Hikory <emmet.hikory@gmail.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Patch selection for porting configtool to wxwidgets2.6
Date: Tue, 15 May 2007 07:39:00 -0000	[thread overview]
Message-ID: <464963AD.3050302@ecoscentric.com> (raw)
In-Reply-To: <9bd2f8970705142331m5dbfcc37x2f42ca735fd4bfb6@mail.gmail.com>

Hi Emmet

Emmet Hikory wrote:

>    I am working on a project to remove all remaining dependencies on
> wxwindows 2.4 from Ubuntu.  Looking through the eCos mailing lists, I
> have encountered two candidate patches that would migrate the
> configtool to wxwidgets2.6, as follows:
> 
> 1)  http://www.xylanta.com/Content/Downloads/eCos/ct_wx260.zip from
> Andy Jackson
> 2)  http://www.mr.inf.tu-dresden.de/eCos/ct060628.patch.gz from Lars
> Poeschel
> 
>    Neither appears to have been committed to CVS, and I wondered if
> there were any specific problems with either patch implementation, and
> also which might be a better starting point when applying a patch for
> use in Ubuntu.

Andy Jackson's patch provides the migration of the configtool to
wxWindows 2.6.x. Lars Poeschel's patch adds autoconfigury which is not
necessarily desirable if you want to develop using an IDE such as
Eclipse/CDT.

I have been experimenting with Andy Jackson's patch - it doesn't work
under Linux (FC5) unmodified. I suggest you start with Andy Jackson's
patch and modify as necessary.

Please keep in touch with your progress...

John Dallaway
eCosCentric Limited

  reply	other threads:[~2007-05-15  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15  6:31 Emmet Hikory
2007-05-15  7:39 ` John Dallaway [this message]
2007-05-15  8:07   ` Emmet Hikory
2007-05-15  8:27     ` 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=464963AD.3050302@ecoscentric.com \
    --to=jld@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=emmet.hikory@gmail.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).