From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] directfb: add host-directfb target for directfb-csource
Date: Fri, 02 Oct 2009 13:28:42 +0200 [thread overview]
Message-ID: <1254482922.3924.16.camel@sven> (raw)
In-Reply-To: <87iqey6o89.fsf@macbook.be.48ers.dk>
On Fri, 2009-10-02 at 13:15 +0200, Peter Korsgaard wrote:
> >>>>> "Sven" == Sven Neumann <s.neumann@raumfeld.com> writes:
>
> Sven> directfb-csource is a code generation tool that may be needed to build
> Sven> other packages. Add host-directfb target that installs directfb-csource
> Sven> in the host_dir.
>
> What exactly needs this? I prefer to not add unused stuff. Could we wait
> until there's an actual use for this?
directfb-csource is very similar to gdk-pixbuf-csource. It creates
header files from images so that they can easily be embedded into the
binary. I do make use of this in one of our packages. At some point I
even plan to release this code under the LGPL, but for now its closed.
Of course I would prefer if the change could be upstream in buildroot,
but if you don't want to add it, then we can maintain it in our branch.
> Sven> +$(STAMP_DIR)/host_directfb_installed: $(STAMP_DIR)/host_directfb_compiled
> Sven> + $(INSTALL) -m 0755 $(DIRECTFB_HOST_DIR)/tools/directfb-csource $(HOST_DIR)/usr/bin
>
> Is directfb-csource the only thing we could ever imagine other packages
> needing? What about the headers/libs for some other host tool?
The other tools are actually useful on the target, but not likely useful
on the host. directfb-csource is the only code-generation tool in there.
Sven
next prev parent reply other threads:[~2009-10-02 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 11:11 [Buildroot] [PATCH] directfb: add host-directfb target for directfb-csource Sven Neumann
2009-10-02 11:15 ` Peter Korsgaard
2009-10-02 11:28 ` Sven Neumann [this message]
2009-10-02 11:40 ` Peter Korsgaard
2009-10-02 12:07 ` Sven Neumann
2009-10-02 12:20 ` Sven Neumann
2009-10-02 13:41 ` Peter Korsgaard
2009-10-03 7:24 ` Peter Korsgaard
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=1254482922.3924.16.camel@sven \
--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