<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-openembedded.git/meta-python/classes/pyo3.bbclass, branch master</title>
<subtitle>Mirror of git.openembedded.org/meta-openembedded</subtitle>
<id>https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-openembedded.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/'/>
<updated>2022-03-16T13:25:28+00:00</updated>
<entry>
<title>meta-python: Clean up recipes and classes that were moved to oe-core</title>
<updated>2022-03-16T13:25:28+00:00</updated>
<author>
<name>Alejandro Enedino Hernandez Samaniego</name>
<email>alejandro.hernandez@linux.microsoft.com</email>
</author>
<published>2022-03-14T02:03:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=bb9d3688f1b5a5f91ee3e1675bd802c5f9c189f3'/>
<id>urn:sha1:bb9d3688f1b5a5f91ee3e1675bd802c5f9c189f3</id>
<content type='text'>
Signed-off-by: Alejandro Enedino Hernandez Samaniego &lt;alejandro.hernandez@linux.microsoft.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: tgamblin &lt;trevor.gamblin@windriver.com&gt;
</content>
</entry>
<entry>
<title>pyo3.bbclass: add class for PyO3 cross-compilation</title>
<updated>2022-01-18T20:53:38+00:00</updated>
<author>
<name>Tim Orling</name>
<email>ticotimo@gmail.com</email>
</author>
<published>2022-01-16T05:28:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-openembedded.git/commit/?id=5c7d63a4377f13e6415fa6e72503b072f898d6a8'/>
<id>urn:sha1:5c7d63a4377f13e6415fa6e72503b072f898d6a8</id>
<content type='text'>
PyO3 provides Rust bindings for Python, including tools for creating native
Python extension modules. Running and interacting with Python code from a
Rust binary is also supported.

This class sets up the cross-compilation environment.

Export PYO3_CROSS, PYO3_CROSS_LIB_DIR, PYO3_CROSS_INCLUDE_DIR and CARGO_BUILD_TARGET
to inform tools like setuptools-rust we are cross-compiling.

Export RUSTFLAGS so cargo can find 'std' and 'core' for target

Dynamically generate PyO3 config file and export PYO3_CONFIG_FILE
absolute path. This is the trick that finally made pyo3 work.

Signed-off-by: Tim Orling &lt;tim.orling@konsulko.com&gt;
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Trevor Gamblin &lt;trevor.gamblin@windriver.com&gt;
</content>
</entry>
</feed>
