[PATCH] Use a hash file for GCC only
Gedare Bloom
gedare at rtems.org
Thu Mar 2 15:37:08 UTC 2017
On Thu, Mar 2, 2017 at 10:26 AM, Sebastian Huber
<sebastian.huber at embedded-brains.de> wrote:
> On 02/03/17 16:23, Gedare Bloom wrote:
>>
>> In a way, I do like that this shows the different gcc-newlib versions
>> we use. It might be nice to add a bit of organization to this hashes
>> file and/or documentation of the procedure for adding/removing
>> entries.
>>
>> Maybe it makes more sense to have a separate file for each version
>> being used, e.g. a gcc-4.8.3 hash file, gcc-4.9.3, gcc-6.0.1, etc?
>> That should make it easier to maintain the hashes.
>>
>> I'll leave it to Chris to decide if this is a suitable compromise.
>
>
> I don't know why this hash stuff caused such an uproar. The hashes are
> invariants of the files. If they ever change something is seriously wrong.
> Things that never change should be defined exactly once in a system.
>
It seems that you stumbled over an unwritten design philosophy. I'm
not picking sides on this, but I do think it is a good idea to
organize the hashes into include files to reduce the copy-paste. I
also think my suggestion of putting them in version-based files
alleviates the "horizontal integration" concern.
> --
> 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
mailing list