Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] orc: new package
Date: Sun, 31 Jul 2011 10:19:27 +0200	[thread overview]
Message-ID: <1312100368.687.4.camel@bender> (raw)
In-Reply-To: <87k4b7uzey.fsf@macbook.be.48ers.dk>

On Sun, 2011-07-24 at 23:44 +0200, Peter Korsgaard wrote:
> >>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
> 
>  Sven> Orc - the Oil Runtime Compiler - is the successor of liboil.
>  Sven> There's a runtime library that is installed in staging and target
>  Sven> and there's a host version that can be built if orcc, the ORC
>  Sven> compiler is needed at build time.
> 
> So presumably we should remove liboil? The only thing using it is
> swfdec, which afaik is long dead upstream.

Agreed.

> Should usr/bin/orcc get removed if !BR2_HAVE_DEVFILES or is it needed
> for anything?

Yes, that makes sense. There's also /usr/bin/orc-bugreport which should
probably be removed as well.

> I've committed with those changes (except for orcc, please advice) -
> Thanks.

I won't find time to do the proposed changes before next week as I am
currently on vacation.


Sven

  reply	other threads:[~2011-07-31  8:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-14  7:32 [Buildroot] new package: orc Sven Neumann
2011-07-14  7:32 ` [Buildroot] [PATCH 1/2] orc: new package Sven Neumann
2011-07-24 21:44   ` Peter Korsgaard
2011-07-31  8:19     ` Sven Neumann [this message]
2011-08-04 19:16       ` Peter Korsgaard
2011-07-14  7:32 ` [Buildroot] [PATCH 2/2] gst-plugins-base: depend on orc if it is enabled Sven Neumann
2011-07-24 21:45   ` Peter Korsgaard
2011-07-31  8:16     ` Sven Neumann

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=1312100368.687.4.camel@bender \
    --to=s.neumann@raumfeld.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox