This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: how to add new target to Binutils source
- From: Nick Clifton <nickc at redhat dot com>
- To: "free.jesse" <free dot jesse at yahoo dot com>
- Cc: binutils at sourceware dot org
- Date: Tue, 24 Jan 2006 10:50:59 +0000
- Subject: Re: how to add new target to Binutils source
- References: <20060123151654.14309.qmail@web37013.mail.mud.yahoo.com>
Hi Jesse,
I am jesse. Now, I have ported GNU Binutils to a
embeded chip and what i wanna do next is to add the
target to Binutils source code. Would you please tell
me how to do.
You will need to agree to assign the copyright to the code that you have
written over to the FSF. You can start this process by filling out the
attached form and emailing it to the FSF. Once this process is complete
any code that you contribute to the FSF will have its copyright also
assigned to the FSF. (Of course any code that you do not contribute
remains your own).
Once the copyright assignment is in place you can contribute the patches
that add support for the embedded chip. Ideally these patches should:
* Come with a short description of what they are. eg "Add support
for chip FOO...".
* Be made against the current development sources in the binutils CVS
repository.
* Include entries for the ChangeLog files in the relevant directories
describing what changes are being made in that directory. (These
entries should be submitted as plain text, not patches, since they very
rarely apply cleanly).
* Follow the GNU Coding standards, so that their style matches the
style of the rest of the code in the binutils sources.
http://www.gnu.org/prep/standards/
* Include an update to the NEWS files in the relevant subdirectories
(ld, gas). The NEWS files are used to make the release notes when we
create official releases, and we like to be able to mention new support
for any chips.
* Include new additions to the GAS and LD testsuites to check the
behaviour of the assembler and linker for this new port.
dose it need to pay any fee?
No this is all free. Well apart from whatever your time may cost you.
who should i contact?
Me :-) But actually all email regarding binutils should be sent to the
binutils list (as you have done), and not to me personally.
Cheers
Nick
---------------------------------------------------------------------------
request-assign.future:
Please email the following information to fsf-records@gnu.org, and we
will send you the assignment form for your past and future changes.
Please use your full name as the subject line of the message.
[What is the name of the program or package you're contributing to?]
[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]
[Do you have an employer who might have a basis to claim to own
your changes? Do you attend a school which might make such a claim?]
[For the copyright registration, what country are you a citizen of?]
[What year were you born?]
[Please write your email address here.]
[Please write your snail address here.]
[Which files have you changed so far, and which new files have you written
so far?]
---------------------------------------------------------------------------