<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot-novena/arch/Config.in.microblaze, branch 2013.05_rc1</title>
<subtitle>build system for the novena open hardware laptop board</subtitle>
<id>https://git.bnewbold.net/buildroot-novena/atom?h=2013.05_rc1</id>
<link rel='self' href='https://git.bnewbold.net/buildroot-novena/atom?h=2013.05_rc1'/>
<link rel='alternate' type='text/html' href='https://git.bnewbold.net/buildroot-novena/'/>
<updated>2012-11-15T15:12:46+00:00</updated>
<entry>
<title>arch: improve definition of gcc mtune, mcpu, etc.</title>
<updated>2012-11-15T15:12:46+00:00</updated>
<author>
<name>Thomas Petazzoni</name>
<email>thomas.petazzoni@free-electrons.com</email>
</author>
<published>2012-11-15T03:53:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.bnewbold.net/buildroot-novena/commit/?id=44c04a2b4aa998e9c52c4d30f45b1ded933b966a'/>
<id>urn:sha1:44c04a2b4aa998e9c52c4d30f45b1ded933b966a</id>
<content type='text'>
As suggested by Yann E. Morin, there is a better way than our current
big Config.in.common to define the gcc mtune, mcpu, march,
etc. values. We can split the setting of those values in each
architecture file, which makes a lot more sense.

Therefore, the Config.in file now creates empty kconfig variables
BR2_ARCH, BR2_ENDIAN, BR2_GCC_TARGET_TUNE, BR2_GCC_TARGET_ARCH,
BR2_GCC_TARGET_ABI and BR2_GCC_TARGET_CPU. The values of those
variables are set by the individual Config.in.&lt;arch&gt; files. This is
possible because such files are now only conditionally included
depending on the top-level architecture that has been selected.

Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
Acked-by: "Yann E. MORIN" &lt;yann.morin.1998@free.fr&gt;
Signed-off-by: Peter Korsgaard &lt;jacmet@sunsite.dk&gt;
</content>
</entry>
</feed>
