From: "Fabian Scheler" <fabian.scheler@gmail.com>
To: "Lars Poeschel" <larsi@wh2.tu-dresden.de>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: configtool development
Date: Fri, 14 Apr 2006 19:20:00 -0000 [thread overview]
Message-ID: <69dd805e0604141220r47c6ff5fl265791817fcaee@mail.gmail.com> (raw)
In-Reply-To: <200604141947.07839.larsi@wh2.tu-dresden.de>
Hello,
I rather think the problems are mainly caused by the wxWidgets
library, aren't they? There were some changes in the wxWidgets API
between versions 2.4.x and 2.6.x driving them incompatible in some
cases, on of these cases apparently is the ecos configtool. Besides
that there are some instructions available on the eCosCentric homepage
(www.ecoscentric.com) that helped me to build the configtool
sucessfully with wxWidgets 2.4.2
Have a nice easter, too.
Ciao, Fabian Scheler
2006/4/14, Lars Poeschel <larsi@wh2.tu-dresden.de>:
> 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
>
next prev parent reply other threads:[~2006-04-14 19:20 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 [this message]
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
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=69dd805e0604141220r47c6ff5fl265791817fcaee@mail.gmail.com \
--to=fabian.scheler@gmail.com \
--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).