You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Aditi Hilbert (JIRA)" <ji...@apache.org> on 2018/02/06 08:06:00 UTC
[jira] [Updated] (MYNEWT-499) newt - APP_NAME value ambiguous for
split images
[ https://issues.apache.org/jira/browse/MYNEWT-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aditi Hilbert updated MYNEWT-499:
---------------------------------
Labels: Newt (was: )
> newt - APP_NAME value ambiguous for split images
> ------------------------------------------------
>
> Key: MYNEWT-499
> URL: https://issues.apache.org/jira/browse/MYNEWT-499
> Project: Mynewt
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: Newt
> Reporter: Christopher Collins
> Assignee: Sterling Hughes
> Priority: Major
> Labels: Newt
>
> Newt automatically creates a few macros on the command line when it builds a target:
> * {{ARCH_<arch-name>}}
> * {{ARCH_NAME="<arch-name>"}}
> * {{APP_<arch-name>}}
> * {{APP_NAME="<arch-name>"}}
> * {{BSP_<arch-name>}}
> * {{BSP_NAME="<arch-name>"}}
> There is a problem with the two APP defines. A split image consists of two apps (the "loader" and the "app"), so there is not a single correct value to specify during compilation.
> There are two issues here:
> * Code cannot rely on consistent values for the APP defines when it is part of a split image
> * Newt performs unnecessary compiling and linking operations for repeat builds of split targets. This is because the command-line invocation changes between builds, as the APP name is not consistent.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)