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

Christopher Collins closed MYNEWT-39.
-------------------------------------
    Resolution: Fixed

The contents of all {{<project-name>.yml}} and {{compiler.yml}} files have been 
migrated to the corresponding {{pkg.yml}} files, and the Newt tool has been 
updated to account for this change.

A few notes:
* Project yml files have been modified to look exactly like any other pkg.yml 
file.  This means:
** The "project" prefix has been converted to "pkg"
** The "pkgs" setting has been renamed to "deps"
* Unlike project files, compiler yml files were not fully transformed into the 
pkg.yml format.  Compiler-specific settings (e.g., "compiler.path.cc", 
"compiler.ld.flags", etc.) retain the "compiler" prefix.

The changes to the Newt tool were of the "quick fix" variety.  While reading a 
project's yml file, the tool simply opens "pkg.yml" when it used to open 
"<project-name>.yml".  The proper fix is to load the project configuration in 
the same way as package configurations, allowing us to remove much of the code 
in project.go.  I did not do this because this would require some major 
restructuring of the newt code, and I would prefer to implement this fix 
incrementally.  In the future, we will likely want to make these major changes.

> Fix confusion between egg & project .yml files
> ----------------------------------------------
>
>                 Key: MYNEWT-39
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-39
>             Project: Mynewt
>          Issue Type: Improvement
>            Reporter: Sterling Hughes
>            Assignee: Christopher Collins
>             Fix For: v0_8_0_beta2
>
>
> Right now the project's need to have egg dependencies in egg.yml for newt egg 
> dependencies, and the newt build system looks for the project's dependencies 
> in the <project>.yml file.  This leads to confusion, and mismatching files.
> This should be unified, by either: 
> a) Removing the <project>.yml file, and just having an egg.yml file.
> b) Only listing project dependencies in either the egg.yml _OR_ the 
> <project>.yml file.
> Personally, I think everything a project does can be encapsulated in an 
> egg.yml file. 



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

Reply via email to