From: John Dallaway <jld@ecoscentric.com>
To: Tom Malcolmson <tom@malcolmson.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: wxWidgets tool
Date: Tue, 02 Oct 2007 08:30:00 -0000 [thread overview]
Message-ID: <4702018A.4080308@ecoscentric.com> (raw)
In-Reply-To: <47010B22.2000503@Malcolmson.com>
Tom
Tom Malcolmson wrote:
> I noticed some patches available here:
> http://www.xylanta.com/WordPress/?page_id=22
> including one to make it work with wxWidgets v2.6.
Coincidentally, I have recently tracked down an issue with the eCos
Configuration Tool when built against wxGTK 2.6.x on Linux. The Xylanta
patches will be checked-in when the necessary copyright assignment is in
place.
> I'm not clear on where the 'official' home of the tool / latest version
> is? And whether the wxWidgets version also depends on cygwin?
The official home is alongside the eCos run-time sources. Ref:
http://ecos.sourceware.org/anoncvs.html
It is necessary to checkout both the "ecos" and "ecos-host" modules from
the CVS repository.
I can confirm that the wxMSW build of the eCos Configuration Tool does
depend on Cygwin.
John Dallaway
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-10-02 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 1:22 [ECOS] " Slide
2007-10-01 8:32 ` [ECOS] " John Dallaway
2007-10-01 9:01 ` [ECOS] " Gary Thomas
[not found] ` <a623f7d10710010620t1db9b23ekb5456c4c0720abf8@mail.gmail.com>
2007-10-01 13:26 ` Gary Thomas
2007-10-01 14:04 ` Slide
2007-10-01 14:58 ` Tom Malcolmson
2007-10-01 15:03 ` Gary Thomas
2007-10-01 19:52 ` Tom Malcolmson
2007-10-02 8:30 ` John Dallaway [this message]
2007-10-02 8:59 ` [ECOS] " Lars Poeschel
2007-10-02 14:07 ` Andy Jackson
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=4702018A.4080308@ecoscentric.com \
--to=jld@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=tom@malcolmson.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).