Separation of RTEMS sources and tool chain patches
sebastian.huber at embedded-brains.de
Tue Sep 30 08:40:19 UTC 2014
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 the tools for a release being held in
> RTEMS and the build system checking the tools however at this point in time I
> do not think is it a good idea to move everything into RTEMS. I have not given
> the idea much consideration but I see issues with the validation process. For
> example the tools and RTEMS can move independently of each other and on head
> this is a little more difficult however with a release things are much more
> stable. This means a dot point release of RTEMS does not require a dot point
> version of tools.
> My view may change as what we have moved too settles and maybe I am just
> hesitant to move too quickly here.
In case you have an RTEMS release and then a tool chain patch change is
necessary, can't you simply do this update in the RTEMS release branch? You
need a branch update anyway to bring in the new INI/XML file describing the
current tool chain intended for this RTEMS version.
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel