You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Sterling Hughes (JIRA)" <ji...@apache.org> on 2016/08/23 21:42:21 UTC

[jira] [Updated] (MYNEWT-323) Newt - Build options precedence hierarchy

     [ https://issues.apache.org/jira/browse/MYNEWT-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sterling Hughes updated MYNEWT-323:
-----------------------------------
    Fix Version/s:     (was: v0_10_0)
                   v1_0_0_beta1

> Newt - Build options precedence hierarchy
> -----------------------------------------
>
>                 Key: MYNEWT-323
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-323
>             Project: Mynewt
>          Issue Type: Bug
>          Components: Newt
>            Reporter: Christopher Collins
>            Assignee: Christopher Collins
>             Fix For: v1_0_0_beta1
>
>
> When two packages specify conflicting build options, it is undefined which one takes effect.  Worse, if two packages specify conflicting cflags (e.g., "-DLOG_LEVEL=0" and "-DLOG_LEVEL=1"), gcc reports an error and aborts the build.
> We should enforce a well-defined precedence hierarchy.  I'm thinking something like this (lowest priority first):
> * Library
> * BSP
> * App
> * Target
> In the case of conflicting options, newt should discard all but the highest priority.  Newt would need to do some simple parsing of cflags to identity conflicts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)