Separation of RTEMS sources and tool chain patches

Chris Johns chrisj at
Mon Sep 29 22:48:34 UTC 2014

On 30/09/2014 3:26 am, Peter Dufault wrote:
> On Sep 29, 2014, at 02:15 , Chris Johns <chrisj at> 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 is ubiquitous and easier to sell.  I use tinyXML2.  TinyXML2 has been complete enough for me, and the footprint is small enough for me even on my target devices.  On the embedded PowerPC MPC5554:

I am happy to have XML added to the report formats produced by the RSB. 
I still think INI is an easier format to handle and what we should embed 
in the RTEMS source tree. The data is not that complex. If this is an 
issue maybe INI and XML can be embedded.


More information about the devel mailing list