Changes between Version 2 and Version 3 of Developer/Removing_a_Port


Ignore:
Timestamp:
Nov 3, 2015, 12:23:36 AM (4 years ago)
Author:
Joel Sherrill
Comment:

Added more

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Removing_a_Port

    v2 v3  
    1616== Removing an Architecture from the Source ==
    1717
    18 Unlike the instructions for [wiki:Developer/Removing_a_BSP Removing a BSP], these instructions assume the reader is familiar with RTEMS Developer Practices and provides a checklist as opposed to detailed instructions. An important facet of removing an architecture is that it will require changes to multiple areas of the RTEMS Project spread across multiple repositories. This makes it more complicated and the developer removing the architecture should be careful, use grep, and update this page as other areas to update are identified:
     18Unlike the instructions for [wiki:Developer/Removing_a_BSP Removing a BSP], these instructions assume the reader is familiar with RTEMS Developer Practices and provides a checklist as opposed to detailed instructions. An important facet of removing an architecture is that it will require changes to multiple areas of the RTEMS Project spread across multiple repositories. This makes it more complicated and the developer removing the architecture should be careful, use grep, and update this page as other areas to update are identified.
    1919
    20 * File a Trac ticket - This should list all tickets associated with removing BSPs within this architecture. All commit messages associated with removing the architecture should reference this ticket number. See [https://devel.rtems.org/ticket/2443 ticket 2443] for a simple example.
     20HINT: In order to be sure you have gotten all the references, be sure to grep for architecture specific defines that are predefined by GCC in the entire source base of each repository.
     21
     22=== Preparation ===
     23* File a Trac ticket - This should list all tickets associated with removing BSPs within this architecture. All commit messages associated with removing the architecture should reference this ticket number. See [https://devel.rtems.org/ticket/2443 ticket 2443] for a simple example. Remember that the ticket should list tickets for each BSP family in this architecture to be removed individually before this architecture can be removed.
    2124
    2225* bootstrap -c - From the top of the RTEMS source tree.
     
    2427* Make a local development branch in git
    2528
     29=== Removing RTEMS Source Code ===
     30
    2631* Remove cpukit/score/cpu/@ARCHITECTURE@ - Commit as a single patch updating ticket.
    2732
    2833* Remove @ARCHITECTURE@ from cpukit/libnetworking - If the architecture has optimized in_cksum code, then this will require editing the files machine/in_cksum.h, netinet/in_cksum.c, and Makefile.am. There may also be files referencing the architecture which need updating. Commit as a single patch updating ticket.
     34
     35* Remove @ARCHITECTURE@ from cpukit/libdl - This may include source code and/or configuration logic. Commit as a single patch updating ticket.
     36
     37* Remove @ARCHITECTURE@ specific code in cpukit/librpc - This should be restricted to the file src/xdr/xdr_float.c. Commit as a single patch updating ticket.
    2938
    3039* Remove c/src/lib/libcpu/@ARCHITECTURE@ - Commit as a single patch updating ticket.
     
    3241* Remove c/src/lib/libbsp/@ARCHITECTURE@ including shared - Commit as a single patch updating ticket.
    3342
     43* Remove @ARCHITECTURE@ references in testsuites - This may include defines in spfatal08, sptask_err03, sptimer_err02, sp35, and others. Be sure to grep for architecture specific defines that are predefined by GCC. Commit as a single patch updating ticket.
     44
     45=== Removing @ARCHITECTURE@ from other RTEMS Project Source Code ===
     46
     47* Check rtems-libbsd - XXX
     48
     49* Check rtems-tools - XXX
     50
     51=== Removing @ARCHITECTURE@ from RTEMS Documentation ===
    3452* Remove @ARCHITECTURE@ from doc/cpu_supplement - This requires removing a file and updating the top level cpu_supplement.t file. There may also be examples using the architecture. Commit as a single patch updating ticket.
    3553
    3654* Remove @ARCHITECTURE@ from doc/user/preface.texi - This requires a manual edit. Commit as a single patch updating ticket.
    3755
    38 XXX tables, RPC, promotional material, architecture table in wiki
     56=== Removing @ARCHITECTURE@ from GNU Tools ===
     57
     58The @ARCHITECTURE@ may be in use by other targets. We are only removing the RTEMS specific bits.
     59
     60NOTE: This will require a copyright assignment to the Free Software Foundation. Many core developers already have this in place and are the likely candidates to perform these tasks.
     61
     62* binutils - XXX
     63
     64* gcc - XXX
     65
     66* newlib - XXX
     67
     68* gdb -- XXX
     69
     70=== Miscellaneous ===
     71
     72* Supported architecture table on Wiki - XXX link
     73
     74* Supported architecture table in introductory presentation (offline)
     75
     76* Review open Trac tickets for architecture and close
     77
     78* ??? what else
     79