Bug 3418 - Update meta-data to use explicit scc references only
Summary: Update meta-data to use explicit scc references only
Status: RESOLVED FIXED
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: linux-yocto (show other bugs)
Version: 1.3
Hardware: x86 Multiple
: Low normal
Target Milestone: 1.4 M3
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-11-13 18:33 UTC by Darren Hart
Modified: 2013-01-18 16:56 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Hart 2012-11-13 18:33:23 UTC 
There are instances of referring to an scc file without the extension:

fri2-standard.scc:
	define KMACHINE fri2
	define KTYPE standard
	define KARCH i386
	
	include ktypes/standard
	...

This leads to confusion and complicates the documentation of the tooling. Better to just require the extension and update the linux-yocto meta-data to be a shining example of how to do it explicitly and properly.
Comment 1 Bruce Ashfield 2012-11-15 16:49:34 UTC 
Updating estimate.
Comment 2 Bruce Ashfield 2013-01-16 05:12:41 UTC 
Conversion is done. Under review and test.
Comment 3 Bruce Ashfield 2013-01-18 16:56:14 UTC 
commit d6e2fffc5cd4529d437ae5e04a21034ce0a3f7ce
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date:   Fri Jan 18 00:19:29 2013 -0500

    linux-yocto/meta: update include statements to explicit .scc format
    
    The kernel tooling can support a "shorthand" method of including other features
    that doesn't require the full filename ending in .scc. This format is confusing
    when compared to the source tree, and is inconsitently use. This commit updates
    all shorthand includes to a full "include <foo>.scc" format.
    
    [YOCTO #3418]
    
    (From OE-Core rev: acf015f079907da8a4f1b80e44bb64bc7696a6ad)
    
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>