[
https://issues.apache.org/jira/browse/MYNEWT-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16011225#comment-16011225
]
ASF subversion and git services commented on MYNEWT-753:
--------------------------------------------------------
Commit 8ac28b9bda2ddcd14094e6fc9bcec3f6618d5370 in incubator-mynewt-newt's
branch refs/heads/master from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=8ac28b9
]
MYNEWT-753 newt - sysinit file inconsistent
In the generated sysinit C file, calls to initialization functions are
sorted by stage number. Within a stage number, the ordering is random,
and varies from one build to the next. The randomness comes from
Golang's random iteration of maps.
This is bad because it prevents repeatable builds, and causes
unnecessary rebuilds.
The fix is to sort alphabetically by package name within a stage number.
So,
* First sort by stage number
* Then sort by package name.
> newt - generated sysinit file inconsistent
> ------------------------------------------
>
> Key: MYNEWT-753
> URL: https://issues.apache.org/jira/browse/MYNEWT-753
> Project: Mynewt
> Issue Type: Bug
> Reporter: Christopher Collins
> Assignee: Christopher Collins
> Fix For: v1_1_0_rel
>
>
> In the generated sysinit C file, calls to initialization functions are sorted
> by stage number. Within a stage number, the ordering is random, and varies
> from one build to the next. The randomness comes from Golang's random
> iteration of maps.
> This is bad because it prevents repeatable builds, and causes unnecessary
> rebuilds.
> The fix is to sort alphabetically by package name within a stage number. So,
> * First sort by stage number
> * Then sort by package name.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
