From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Seth Bollinger <seth.boll@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Recipes for building ruby modules (rake, gems, etc.)
Date: Tue, 12 Feb 2013 14:05:40 +0000 [thread overview]
Message-ID: <7914520.L5PIRPJvTF@helios> (raw)
In-Reply-To: <CA+JN8xNsJ-74AP6g30Bmt7u4Qg2PWC46E-s3ZS5_mFKgUhyKSg@mail.gmail.com>
On Saturday 01 September 2012 08:54:11 Seth Bollinger wrote:
> I have a few ruby modules I need to create recipes for. Are there any that
> already exist to run rake and gem building tasks (I need to build C
> extensions as well)? I spent some time looking, but didn't find any. I
> would like to reuse work before trying to roll my own.
Hi, I know this is quite an old post but in case you haven't seen, we now have
a meta-ruby layer in the meta-openembedded repository which at least has the
beginnings of ruby support. We'd welcome patches to improve this if you have
anything beyond what's there.
http://cgit.openembedded.org/meta-openembedded/tree/meta-ruby
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-02-12 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 13:54 Recipes for building ruby modules (rake, gems, etc.) Seth Bollinger
2013-02-12 14:05 ` Paul Eggleton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7914520.L5PIRPJvTF@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=seth.boll@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.