From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH][omniorb]
Date: Fri, 05 Mar 2010 08:27:25 +0100 [thread overview]
Message-ID: <4B90B25D.6050609@balister.org> (raw)
In-Reply-To: <40d782961002250808h3faf16e4yc36e8e36199af1c1@mail.gmail.com>
On 02/25/2010 05:08 PM, majo huber wrote:
> Hi@all,
>
> The attached files are a newer recipie for omniorb (4.1.4 instead of 4.0.7).
> I'd kinly request if someone could push it to the dev branch.
OK, I've pushed this. I know the recipe needs converting to
BBCLASSEXTEND. When I have some time, I'll look into it. The -native
recipe is really more of a cross recipe since the only thing really
needed is an idl compiler that runs on the build machine to convert idl
files to c++ files.
Philip
>
> Thanks in advance,
> majo
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-03-05 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:08 [PATCH][omniorb] majo huber
2010-02-26 1:08 ` [PATCH][omniorb] Philip Balister
2010-03-05 7:27 ` Philip Balister [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=4B90B25D.6050609@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
/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.