linux/meta-cloud-services.git/classes, branch wrynose

rubyv2.bbclass: strip native RPATHs from gem shared objects

2026-04-08T16:13:11+00:00

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

ruby.bbclass: copy spec files if present in UNPACKDIR

2024-10-12T01:37:41+00:00

Signed-off-by: Bruce Ashfield

rubyv2: copy gemspec files if provided

2024-10-12T01:16:45+00:00

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

ruby/rubyv2: add new rubyv2 bbclass and support external extconf

2024-10-11T20:14:43+00:00

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

ruby: package plugins in main package

2024-10-09T23:31:28+00:00

Signed-off-by: Bruce Ashfield

global: overrides conversion

2021-08-01T03:49:54+00:00

Signed-off-by: Bruce Ashfield

Added SRCNAME variable to allow bitbake recipe unfriendly gem names

2020-02-27T22:15:56+00:00

Signed-off-by: Nathan Hartman Signed-off-by: Bruce Ashfield

ruby.bbclass: pass LDFLAGS via dldflags to avoid QA warnings

2016-07-25T03:08:07+00:00

Ruby makes use of the lesser known DLDFLAGS to compose flags passed to the linker. Since DLDFLAGS is composed of arch, ldflags and dldflags instead of overwriting DLDFLAGS we drop the correct flags into dldflags. (lowercase vs uppercase) This will avoid the following QA warnings, such as: No GNU_HASH in the elf binary: './tmp/work/core2-64-overc-linux/ruby-shadow/2.4.1-r0/packages-split/ruby-shadow/usr/lib64/ruby/gems/2.2.0/gems/ruby-shadow-2.4.1/lib/shadow.so' No GNU_HASH in the elf binary: './tmp/work/core2-64-overc-linux/ruby-shadow/2.4.1-r0/packages-split/ruby-shadow/usr/lib64/ruby/gems/2.2.0/extensions/x86_64-linux/2.2.0/ruby-shadow-2.4.1/shadow.so' [ldflags] Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

ruby: fix TypeError exception triggered by python3

2016-06-07T13:40:46+00:00

The error appears as follows: ERROR: Failure expanding variable RUBY_GEM_VERSION, expression was ${@get_rubygemsversion("build/tmp/sysroots/x86_64-linux/usr/bin")} which triggered exception TypeError: can't use a string pattern on a bytes-like object Adding an explicit utf-8 decode makes it work again. Similar fixes appear in git://git.pokylinux.org/poky 3e309e0aad Signed-off-by: Paul Gortmaker Signed-off-by: Bruce Ashfield

ruby-shadow: Work around cross compile gem problem

2016-01-19T13:50:53+00:00

Prior to this commit it is not possible to cross build a ruby gem. In fact even on the x86 system the object files for the native gem are generated with the wrong compiler (the host compiler instead of the cross compiler). A better way to fix this in the future would be to use only gems that supported cross compile tool called rake. For now the bbclass can modify the extconf.rb just before creating the gem and insert some code into the Makefile so as to honor the cross compile environment. Signed-off-by: Jason Wessel Signed-off-by: Bruce Ashfield