<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-cloud-services.git/classes/rubyv2.bbclass, branch wrynose</title>
<subtitle>Mirror of git.yoctoproject.org/meta-cloud-services.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=wrynose</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/atom?h=wrynose'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/'/>
<updated>2026-04-08T16:13:11+00:00</updated>
<entry>
<title>rubyv2.bbclass: strip native RPATHs from gem shared objects</title>
<updated>2026-04-08T16:13:11+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2026-04-08T15:51:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=e7f77af2253d2ddc75cf8f7cd1515a58b8971e3e'/>
<id>urn:sha1:e7f77af2253d2ddc75cf8f7cd1515a58b8971e3e</id>
<content type='text'>
Ruby gem native extensions embed the build-time sysroot RPATH in
their .so files, which fails the rpaths QA check. Use chrpath to
strip these after install.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>rubyv2: copy gemspec files if provided</title>
<updated>2024-10-12T01:16:45+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2024-10-12T01:16:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=4c85c6d55a3d1682464735bf427ffc78723d1ed0'/>
<id>urn:sha1:4c85c6d55a3d1682464735bf427ffc78723d1ed0</id>
<content type='text'>
Rather than generating a spec file from a gem (which we
don't have when building from source) or patching it in,
it is easier if we just provide it on the SRC_URI and
copy it into place.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
<entry>
<title>ruby/rubyv2: add new rubyv2 bbclass and support external extconf</title>
<updated>2024-10-11T20:14:43+00:00</updated>
<author>
<name>Bruce Ashfield</name>
<email>bruce.ashfield@gmail.com</email>
</author>
<published>2024-10-11T19:44:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-cloud-services.git/commit/?id=dc37ea052ed74321c5244938f8d702372f663776'/>
<id>urn:sha1:dc37ea052ed74321c5244938f8d702372f663776</id>
<content type='text'>
When building/installing gems with native components, the target
OS and cross compile settings were not correctly being picked up.

Enhance the existing bbclass with the ability to copy a extconf.rb
from UNPACKDIR, so a recipe can specify fixes in it's own copy of
the file.

We also bring in a class from meta-rubygems which has more advanced
cross compile settings. There are a few minor modifications to
this class (copying of extconf.rb) and some spec generation. But
it is now available if the basic ruby class cannot compile and install
a gem.

Signed-off-by: Bruce Ashfield &lt;bruce.ashfield@gmail.com&gt;
</content>
</entry>
</feed>
