#3615 assigned enhancement

[Wiki]Update data on development tools and Find a new home for it.

Reported by: shashvat jain Owned by: Chris Johns
Priority: high Milestone: 5.1
Component: admin Version: 5
Severity: normal Keywords: Wiki
Cc: Blocked By:
Blocking:

Description

https://devel.rtems.org/wiki/TBR/Review/ToolStatus
This page's data is very old and needs to be updated so that it can be added to the wiki with a link to the home page name "Development Tools".

All the data about the tools on the page must be updated to the latest used by RTEMS 5 , this new page can either be added to the page https://devel.rtems.org/wiki/Tools_Used or be made into a separate page altogether .
Advice on the placement of the new page is needed.

Change History (8)

comment:1 Changed on Nov 22, 2018 at 3:02:16 PM by Gedare

Owner: set to Chris Johns
Status: newassigned

comment:2 Changed on Nov 22, 2018 at 3:56:20 PM by Joel Sherrill

Given the age of this information, I would say delete the page and fix references. Is there anything of value left in it?

comment:3 Changed on Nov 23, 2018 at 12:27:54 AM by Chris Johns

I can see no value in either page. Please delete the pages and close this ticket.

comment:4 Changed on Nov 23, 2018 at 3:39:39 AM by 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?

comment:5 in reply to:  4 ; Changed on Nov 23, 2018 at 3:51:02 AM by Chris Johns

Replying to 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.

comment:6 in reply to:  5 ; Changed on Nov 23, 2018 at 6:09:02 AM by shashvat jain

Replying to Chris Johns:

Replying to 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?

comment:7 in reply to:  6 ; Changed on Nov 25, 2018 at 12:08:37 AM by Chris Johns

Replying to shashvat jain:

1)We may add the page for the current version under development 5

What happens for RTEMS 6 or 7 etc?

2)Instead of a tool matrix , we can mention all the tools shared by architecures like gdb , gcc newlib , g++ , binutils , etc .

This changes all the time.

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.

We have this in the documentation ...

https://docs.rtems.org/branches/master/user/tools/index.html

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

No I do not think it is worth updating. A better solution is add to the RSB a way to generate the reports we need.

Chris

comment:8 in reply to:  7 Changed on Nov 25, 2018 at 6:58:35 AM by shashvat jain

Replying to Chris Johns:

Replying to shashvat jain:

1)We may add the page for the current version under development 5

What happens for RTEMS 6 or 7 etc?

2)Instead of a tool matrix , we can mention all the tools shared by architecures like gdb , gcc newlib , g++ , binutils , etc .

This changes all the time.

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.

We have this in the documentation ...

https://docs.rtems.org/branches/master/user/tools/index.html

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

No I do not think it is worth updating. A better solution is add to the RSB a way to generate the reports we need.

Chris

All my doubts are solved , I have no reason to stop you from closing this Ticket .
Thank you

Note: See TracTickets for help on using tickets.