| Age | Commit message (Collapse) | Author |
|---|
|
This effectively reverts commit
4e8853ca05f797281469ae7c7ce0c0b3ccf0d7c1 [bundler: Fix QA new Error]
The original QA error is now handled by changes to the ruby.bbclass to
properly handle build_info and extensions directories that Ruby 2.0.0
now creates while installing gems.
This revert isn't specifically required but by removing this broad
definition of FILES the hope is that other ruby recipes won't copy
this behavior which can actually lead to other QA errors/warnings,
depending on what gets installed in the build_info and extensions
directories.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
add depends for git.
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
ERROR: QA Issue: bundler: Files/directories were installed but not shipped
/usr/lib/ruby/gems/2.2.0/build_info
/usr/lib/ruby/gems/2.2.0/extensions [installed-vs-shipped]
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
In order to allow the building of gems we have created a
ruby.bbclass. The building of gems is much like the building of python
packages in that we rely on building up -native gems in order to
facilitate the cross compiling of the gems that will be built for the
target. When dependencies exist between gems they must be satisfied by
the -native gems installed in the host sysroot. This approach is
feasible since the build process is able to query installed gems
without being affected by the ARCH they were built for. At this point
I have yet to come across a situation where the assumption associated
with this approach have failed but so far focus has only been on x86
and x86-64 builds.
The recipes which inherit the ruby.bbclass can optionally define a BPV
in the case where the gemspec version doesn't always map 1:1 to the
PV. This situation has only been encountered on a few occasions so
the class has been made to default BPV to PV.
To demonstrate the ruby.bbclass in use we have included a recipe to
build the bundler gem. Bundler can be used on a running target to
install gems from rubygems.org, which can be useful in itself when you
don't have recipes available for gems but want to try installing and
running pre-built gems.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
Mark Asselstine
Armin Kuster