public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Andy Jackson" <andy@grapevinetech.co.uk>
To: <ecos-devel@ecos.sourceware.org>
Cc: "Lars Poeschel" <larsi@wh2.tu-dresden.de>
Subject: Re: configtool development
Date: Mon, 01 May 2006 14:21:00 -0000	[thread overview]
Message-ID: <001c01c66d2a$84a2e5c0$9701a8c0@Kimbara> (raw)
In-Reply-To: <200604141947.07839.larsi@wh2.tu-dresden.de>

Hi,

Apologies for the late response. Patches to enable Configtool compilation 
with wxWidgets 2.6.x can be found at our web site:

http://www.xylanta.com

in the Downloads section. My build environment is Cygwin, so your mileage 
may vary, however if they prove stable, then I will submit them for 
inclusion in the repository.

Kind regards,

    Andy..

----- Original Message ----- 
From: "Lars Poeschel" <larsi@wh2.tu-dresden.de>
To: <ecos-devel@ecos.sourceware.org>
Sent: Friday, April 14, 2006 6:47 PM
Subject: configtool development


> Hello!
>
> I am working on ecos for a study project. Therefore I'd like to build the 
> gui
> configtool from source. I failed on my Linux Debian Testing System.
> I found some problems with the Makefile in
> ecos/host/tools/configtool/standalone/wxwin. I also noticed issues with
> UNICODE and compatibilty with the recent wxWidgets 2.6.3.
> In the next days I will try to fix this to have configtool build correctly
> with wxWidgets 2.6.3. Is someone other working on this ? Is this work
> welcome ?
> Maybe later I will fix the Makefile, possibly working with 
> autoconf/automake.
>
> Have a nice easter,
>
> Lars Poeschel 

  parent reply	other threads:[~2006-05-01 14:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2006-07-03  9:38 Lars Poeschel
2006-07-03 10:18 ` 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='001c01c66d2a$84a2e5c0$9701a8c0@Kimbara' \
    --to=andy@grapevinetech.co.uk \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=larsi@wh2.tu-dresden.de \
    /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).