<feed xmlns='http://www.w3.org/2005/Atom'>
<title>multitech-oe.git/classes/distutils-native-base.bbclass, branch multitech-corecdp-1.x</title>
<subtitle>Multi-Tech CoreCDP 1.x OpenEmbedded Tree</subtitle>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/multitech-oe.git/'/>
<entry>
<title>distutils-base.bbclass: Move common functionality to distutils-common-base.bbclass</title>
<updated>2009-03-24T21:01:30+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2009-03-24T21:01:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.multitech.net/cgit/multitech-oe.git/commit/?id=0faff8720150863ff38132f87ef65721fcb86dc1'/>
<id>0faff8720150863ff38132f87ef65721fcb86dc1</id>
<content type='text'>
	Create a new class distutils-common-base.bbclass which holds the common
	parts that can be used in native and target packages which need to use
	distutils funtionality.

	rpm, libxml2, zope are currently using them and needed to use
	distutils-native-base for native recipes.

	rpm and libxml need to defer the processing of certain configure
	parameters which we evaluate using python. So we need to have python-native
	built before we can process them. Hence we can not use EXTRA_OECONF
	which is a python variable and gets expanded during parsing recipes
	and ofcourse we have not yet built python-native.

	We pass these extra options as a separate shell variable to do_configure
	which we evaluate when that task is executing.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
	Create a new class distutils-common-base.bbclass which holds the common
	parts that can be used in native and target packages which need to use
	distutils funtionality.

	rpm, libxml2, zope are currently using them and needed to use
	distutils-native-base for native recipes.

	rpm and libxml need to defer the processing of certain configure
	parameters which we evaluate using python. So we need to have python-native
	built before we can process them. Hence we can not use EXTRA_OECONF
	which is a python variable and gets expanded during parsing recipes
	and ofcourse we have not yet built python-native.

	We pass these extra options as a separate shell variable to do_configure
	which we evaluate when that task is executing.
</pre>
</div>
</content>
</entry>
</feed>
