From: Corey Ashford <cjashfor@us.ibm.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: New PowerPC-specific Eclipse CDT plugin for Eclipse needs a home
Date: Wed, 20 Dec 2006 14:03:58 -0800 [thread overview]
Message-ID: <4589B34E.6020901@us.ibm.com> (raw)
Kumar Gala wrote:
> On Dec 20, 2006, at 2:34 PM, Corey Ashford wrote:
>
>> Hello,
>>
>> I'm new to this mailing list (and the penguinppc web site). I've just
>> finished up a first version of a PowerPC-specific plug-in for the
>> Eclipse C/C++ Development Tooling plug-in.
>>
>> This plug-in adds most of the PowerPC specific GNU C/C++ compiler
>> switches, as well as switches needed for the assembler and for linking
>> (using gcc).
>>
>> At this point, eclipse.org will not host it as they do not have
>> target-specific plug-ins yet. They may eventually.
>>
>> In the meantime, I'm looking for a place to host this plug-in and
>> would
>> be interested in getting some feedback on the content and quality
>> of it,
>> because this is first cut.
>>
>> Thanks for your consideration,
>>
>> - Corey
>
> When you say host what exactly are you looking for? How about
> something like savannah.org or sourceforge.net?
>
> - k
Hi Kumar,
I was thinking there might be some place on penguinppc, but those others
sound like a good idea too. I will look into those.
Thanks for the suggestions!
- Corey
--
Corey Ashford
Software Engineer
IBM Linux Technology Center, Linux Toolchain
Beaverton, OR
503-578-3507
cjashfor@us.ibm.com
next reply other threads:[~2006-12-20 22:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 22:03 Corey Ashford [this message]
2006-12-20 22:23 ` New PowerPC-specific Eclipse CDT plugin for Eclipse needs a home Benjamin Herrenschmidt
2006-12-22 1:20 ` Hollis Blanchard
2006-12-23 21:32 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2006-12-23 1:53 Corey Ashford
2006-12-20 20:34 Corey Ashford
2006-12-20 21:10 ` Kumar Gala
2006-12-21 3:20 ` Stephen Rothwell
2006-12-21 13:04 ` Matt Sealey
2006-12-21 14:30 ` Ben Warren
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=4589B34E.6020901@us.ibm.com \
--to=cjashfor@us.ibm.com \
--cc=linuxppc-dev@ozlabs.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 NNTP newsgroup(s).