how to add new target to Binutils source

[Nick Clifton]

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

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: future
URL: <https://sourceware.org/pipermail/binutils/attachments/20060124/62b200fb/attachment.ksh>