Re: Separation of RTEMS sources and tool chain patches

2014-09-30 Thread Chris Johns
On 30/09/2014 6:40 pm, Sebastian Huber wrote: On 29/09/14 08:15, Chris Johns wrote: Why do we not move the tool chain patches back to the RTEMS sources? I think it would be nice if you can check out a particular RTEMS version and then use the RSB and say: build me the tool chain for this versi

Re: Separation of RTEMS sources and tool chain patches

2014-09-30 Thread Chris Johns
On 30/09/2014 6:28 pm, Sebastian Huber wrote: On 30/09/14 00:48, Chris Johns wrote: On 30/09/2014 3:26 am, Peter Dufault wrote: On Sep 29, 2014, at 02:15 , Chris Johns wrote: I can add the scripts to INI file format. I feel XML is too heavy a requirement for parsing. There is a single C++ f

Re: Separation of RTEMS sources and tool chain patches

2014-09-30 Thread Sebastian Huber
On 29/09/14 08:15, Chris Johns wrote: Why do we not move the tool chain patches back to the RTEMS sources? I think it would be nice if you can check out a particular RTEMS version and then use the RSB and say: build me the tool chain for this version. I am ok with the INI file that defines t

Re: Separation of RTEMS sources and tool chain patches

2014-09-30 Thread Sebastian Huber
On 30/09/14 00:48, Chris Johns wrote: On 30/09/2014 3:26 am, Peter Dufault wrote: On Sep 29, 2014, at 02:15 , Chris Johns wrote: I can add the scripts to INI file format. I feel XML is too heavy a requirement for parsing. There is a single C++ file that does it and Python handles the format

Re: Separation of RTEMS sources and tool chain patches

2014-09-29 Thread Chris Johns
On 30/09/2014 3:26 am, Peter Dufault wrote: On Sep 29, 2014, at 02:15 , Chris Johns wrote: I can add the scripts to INI file format. I feel XML is too heavy a requirement for parsing. There is a single C++ file that does it and Python handles the format easily. I also think it is easier to re

Re: Separation of RTEMS sources and tool chain patches

2014-09-29 Thread Peter Dufault
On Sep 29, 2014, at 02:15 , Chris Johns wrote: > I can add the scripts to INI file format. I feel XML is too heavy a > requirement for parsing. There is a single C++ file that does it and > Python handles the format easily. I also think it is easier to read. Yes, INI is easier to read but XML

Re: Separation of RTEMS sources and tool chain patches

2014-09-28 Thread Chris Johns
On 26/09/2014 7:40 pm, Sebastian Huber wrote: On 18/09/14 00:58, Chris Johns wrote: On 17/09/2014 6:49 pm, Sebastian Huber wrote: currently the RTEMS sources contain no reference to the intended tool chain versions (Binutils, Newlib, GCC, GDB) and patches for the tools. This is specified elsew

Re: Separation of RTEMS sources and tool chain patches

2014-09-26 Thread Sebastian Huber
On 18/09/14 00:58, Chris Johns wrote: On 17/09/2014 6:49 pm, Sebastian Huber wrote: currently the RTEMS sources contain no reference to the intended tool chain versions (Binutils, Newlib, GCC, GDB) and patches for the tools. This is specified elsewhere, for example in the RTEMS tools repository

Re: Separation of RTEMS sources and tool chain patches

2014-09-17 Thread Chris Johns
On 17/09/2014 6:49 pm, Sebastian Huber wrote: currently the RTEMS sources contain no reference to the intended tool chain versions (Binutils, Newlib, GCC, GDB) and patches for the tools. This is specified elsewhere, for example in the RTEMS tools repository. The RSB has the ability to report

Separation of RTEMS sources and tool chain patches

2014-09-17 Thread Sebastian Huber
Hello, currently the RTEMS sources contain no reference to the intended tool chain versions (Binutils, Newlib, GCC, GDB) and patches for the tools. This is specified elsewhere, for example in the RTEMS tools repository. Since the RTEMS version is tightly coupled to a particular tool chain ve