[RTEMS Project] #3615: [Wiki]Update data on development tools and Find a new home for it.

[RTEMS trac]

#3615: [Wiki]Update data on development tools and Find a new home for it.
---------------------------+--------------------------
 Reporter:  shashvat jain  |       Owner:  Chris Johns
     Type:  enhancement    |      Status:  assigned
 Priority:  high           |   Milestone:  5.1
Component:  admin          |     Version:  5
 Severity:  normal         |  Resolution:
 Keywords:  Wiki           |  Blocked By:
 Blocking:                 |
---------------------------+--------------------------

Comment (by shashvat jain):

 Replying to [comment:5 Chris Johns]:
 > Replying to [comment:4 shashvat jain]:
 > > Does this wiki already has a "development tools" page , the
 information is quite old , is it worth deleting these and adding a new one
 which are updated?
 >
 > No it does have one. A wiki page for this type of thing for RTEMS is
 difficult to get right. The issues are:
 > 1. Each version of RTEMS has a specific set of tools so a single page
 would not work.
 > 2. The tool matrix is complex with different versions of the various
 tools for different architectures and then differences for these for
 different hosts. You can see this my looking at the build output from the
 RSB on the `build` list, for example a recent ARM build
 (https://lists.rtems.org/pipermail/build/2018-November/001318.html)  The
 last section is the build report that lists the files and patches.
 > 3. The term "Tools" covers the compiler and its tools plus it now it
 includes the various eco-system tools. The size of the page would be large
 and getting all the detail right would be an busy long term task.

 1)We may add the page for the current version under development 5
 2)Instead of a tool matrix , we can mention all the tools shared by
 architecures like gdb , gcc newlib , g++ , binutils , etc .
 3)If the term tools covers so much then can we make a document covering
 everything about the compiler ? , if we spend some time and make it , the
 next step left would be just to update it timely when the version changes.

 Do you think it is worth the time and effort of updating?

--
Ticket URL: <http://devel.rtems.org/ticket/3615#comment:6>
RTEMS Project <http://www.rtems.org/>
RTEMS Project