<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-mingw.git/classes, branch pyro</title>
<subtitle>Mirror of git.yoctoproject.org/meta-mingw.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-mingw.git/atom?h=pyro</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-mingw.git/atom?h=pyro'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-mingw.git/'/>
<updated>2016-02-01T22:59:08+00:00</updated>
<entry>
<title>toolchain-scripts-mingw32.bbclass: Update to match YP 2.0 release</title>
<updated>2016-02-01T22:59:08+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@windriver.com</email>
</author>
<published>2015-11-29T17:04:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-mingw.git/commit/?id=ee65e77639b406fd267cbceddafda03a35223525'/>
<id>urn:sha1:ee65e77639b406fd267cbceddafda03a35223525</id>
<content type='text'>
The environment script generatation is updated to match YP 2.0 version.

In addition, there was an error in the way the EXTRAPATH component was being
generated.

Signed-off-by: Mark Hatle &lt;mark.hatle@windriver.com&gt;
</content>
</entry>
<entry>
<title>toolchain-scripts-mingw32: Use short paths (8.3)</title>
<updated>2016-02-01T22:59:08+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@windriver.com</email>
</author>
<published>2015-02-25T20:24:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-mingw.git/commit/?id=35704684c8fda92ca7d909ed9f33db8d7daf4d26'/>
<id>urn:sha1:35704684c8fda92ca7d909ed9f33db8d7daf4d26</id>
<content type='text'>
When using standard paths, the user may end up exceeding the path length to
some toolchain helper libraries (DLLs) and binaries.

By switching to using the "short path", we can avoid this in many more cases.

If the user does exceed the path length, their only option will be to move
the SDK lower in their directory tree.

Signed-off-by: Mark Hatle &lt;mark.hatle@windriver.com&gt;
</content>
</entry>
<entry>
<title>meta-environment: Update environment files to batch files</title>
<updated>2016-02-01T22:59:08+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@windriver.com</email>
</author>
<published>2015-01-07T00:20:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-mingw.git/commit/?id=9e9f8b01736c00bb061ec56404956fbb4dedef6a'/>
<id>urn:sha1:9e9f8b01736c00bb061ec56404956fbb4dedef6a</id>
<content type='text'>
Since the environment .sh files can't be used on a normal windows machine,
change to providing .bat files instead.  The same mechanisms normally used
can be used on the Windows command line. i.e.

Unix way:
$ source environment-setup-armv5te-wrs-linux-gnueabi.sh
$ $CC hello.c

Win32 way:
C:\Users\mhatle\win-sdk&gt;environment-setup-armv5te-wrs-linux-gnueabi.bat

C:\Users\mhatle\win-sdk&gt;%CC% hello.c

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