<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-xilinx.git/meta-xilinx-standalone/classes/xlnx-standalone.bbclass, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/meta-xilinx.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/'/>
<updated>2022-01-23T20:17:00+00:00</updated>
<entry>
<title>xilinx-microblaze.bbclass: Fail if meta-microblaze is not included</title>
<updated>2022-01-23T20:17:00+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2022-01-22T16:25:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=38d62b412d0dab00dc01d81521c0fd0d06188e23'/>
<id>urn:sha1:38d62b412d0dab00dc01d81521c0fd0d06188e23</id>
<content type='text'>
When the user uses a microblaze tune, we need to check if meta-microblaze is
part of their build.  If not stop, and tell them they need to add it.

meta-microblaze is not a layers dependency as it is not needed for most
builds.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
</feed>
