From: John Dallaway <jld@ecoscentric.com>
To: Andy Jackson <andy@xylanta.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Configtool patch for wxWidgets 2.6.x
Date: Fri, 21 Sep 2007 14:23:00 -0000 [thread overview]
Message-ID: <46F3D3C2.4030803@ecoscentric.com> (raw)
In-Reply-To: <44571EDA.5070704@ecoscentric.com>
Hi Andy
John Dallaway wrote:
> Andy Jackson wrote:
>
>> 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.
>
> Thank you for the pointer to your configtool patches. I will review
> these shortly. The patch for building against wxWidgets 2.6.x is
> particularly welcome...
I have finally tracked down an obscure issue with running the eCos
Configuration Tool on Linux using wxWidgets 2.6.x and your
ct_wx260.patch. Due to the size of your patch, a copyright assignment
will be required before I can check it in. A guide to copyright
assignment for eCos is available at:
http://ecos.sourceware.org/patches-assignment.html
However, some of the detail on that page has now been made obsolete by
very recent events. Instead of assigning copyright to eCosCentric, it is
now required to assign copyright to the Free Software Foundation (FSF).
This copyright assignment is a requirement in order for the FSF to
defend eCos from license abuses.
To request an assignment form, please fill in the form in the following
link and e-mail it to <assign@gnu.org>:
http://cvs.savannah.gnu.org/viewvc/gnulib/doc/Copyright/request-assign.future?revision=1&root=gnulib
Thank you for the contribution!
John Dallaway
parent reply other threads:[~2007-09-21 14:23 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <44571EDA.5070704@ecoscentric.com>]
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=46F3D3C2.4030803@ecoscentric.com \
--to=jld@ecoscentric.com \
--cc=andy@xylanta.com \
--cc=ecos-maintainers@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).