<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>4782</bug_id>
          
          <creation_ts>2013-06-26 11:16:34 +0000</creation_ts>
          <short_desc>Remove meta-toolchain-gmae</short_desc>
          <delta_ts>2014-03-21 13:57:02 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>devtools / tool chain</component>
          <version>1.4</version>
          <rep_platform>All</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard>21 March 2014: Reset documentation flag to &quot;No&quot;</status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>1.6</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Ross Burton">ross.burton</reporter>
          <assigned_to name="Ross Burton">ross.burton</assigned_to>
          <cc>elizabeth.flanagan</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
    
    <cc>srifenbark</cc>
    
    <cc>yi.zhao</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>No (bug/feature does not impact docs)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>34157</commentid>
    <comment_count>0</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-06-26 11:16:34 +0000</bug_when>
    <thetext>meta-toolchain-gmae should be removed.  It&apos;s not a GNOME Mobile toolchain because a) GNOME Mobile doesn&apos;t exist anymore and b) the libraries in the SDK isn&apos;t the complete GNOME Mobile platform, so the chances that it&apos;s useful to anyone is pretty slim.  Thanks to the &quot;populate_sdk&quot; task everyone can generate a toolchain specifically for their image, and for QA purposes we can just use core-image-sato.

So, here&apos;s a plan:

1) Add core-image-sato -c populate_sdk to the autobuilder.  Note that this is in addition to meta-toolchain-gmae here, not replace.
2) Update QA testcases to use core-image-sato&apos;s SDK, not meta-toolchain-gmae
3) Remove meta-toolchain-gmae from autobuilder
4) Remove meta-toolchain-gmae and friends from oe-core.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>34167</commentid>
    <comment_count>1</comment_count>
    <who name="Yi Zhao">yi.zhao</who>
    <bug_when>2013-06-27 07:57:31 +0000</bug_when>
    <thetext>Hi Ross,

There is a command &quot;bitbake meta-toolchain-sdk&quot; to generate the toolchain tarball. Now the meta-toolchain-sdk is equal to meta-toolchain-gmae. If we remove the meta-toolchain-gmae, can we use this command &quot;bitbake meta-toolchain-sdk&quot; instead of &quot;bitbake core-image-sato -c populate_sdk&quot; ?

Thanks,
Yi</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>34169</commentid>
    <comment_count>2</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-06-27 09:04:45 +0000</bug_when>
    <thetext>meta-toolchain-sdk is the same as -gmae, so that doesn&apos;t actually gain us anything apart from removing the letters &quot;gmae&quot;.

So no, let&apos;s encourage everyone else to use a proper SDK by using a proper SDK ourselves, and use core-image-sato -c populate_sdk.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>34171</commentid>
    <comment_count>3</comment_count>
    <who name="Richard Purdie">richard.purdie</who>
    <bug_when>2013-06-27 09:24:37 +0000</bug_when>
    <thetext>The populate_sdk task was introduced to remove the need for these &quot;toolchain-sdk&quot; style recipes so removal of this is really a logical conclusion to various developments that have been made.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>34172</commentid>
    <comment_count>4</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-06-27 10:10:37 +0000</bug_when>
    <thetext>*Untested* patch for (1) sent.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39238</commentid>
    <comment_count>5</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-12-05 11:12:26 +0000</bug_when>
    <thetext>Patches sent.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>39322</commentid>
    <comment_count>6</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2013-12-10 15:45:07 +0000</bug_when>
    <thetext>Removed from oe-core as of c44fa1206c965054e8e4d316969a8e291cfef590.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>41574</commentid>
    <comment_count>7</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2014-03-21 13:49:03 +0000</bug_when>
    <thetext>Scott says the docs don&apos;t mention &quot;gmae&quot; at all.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>41575</commentid>
    <comment_count>8</comment_count>
    <who name="Scott Rifenbark">srifenbark</who>
    <bug_when>2014-03-21 13:57:02 +0000</bug_when>
    <thetext>Hi, 

I had purged the doc set of this stuff quite some time ago.  So it turns out there is no need for a documentation change for this bug.

Turning the documentation flag to &quot;No&quot;

Scott</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>