From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ParaGUI package?
Date: Fri, 10 Jan 2014 07:01:11 +0800 [thread overview]
Message-ID: <20140110070111.483dd1a9@skate> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D8817E6C50F@P3PWEX4MB008.ex4.secureserver.net>
Dear Hartley Sweeten,
On Thu, 9 Jan 2014 22:37:40 +0000, Hartley Sweeten wrote:
> I was finally able to get paragui to compile with Buildroot using a POST_PATCH_HOOKS
> like was just done for the sdl package:
>
> define PARAGUI_RUN_AUTOGEN
> cd $(@D) && ./autogen.sh
> endef
>
> PARAGUI_POST_PATCH_HOOKS += PARAGUI_RUN_AUTOGEN
Humm, ok. This is not the nicest thing in the world, but oh well.
> Doing this I only needed 2 patches.
> 1) to use the correct sdl-config
> 2) to include <ostream> in a source file (I think this is needed because of a gcc 4.3.3 bug)
>
> I was also able to get the package to compile using AUTORECONF = YES but that
> needed a lot more patches.
Which patches?
>
> I can post the patch to add the paragui package but there is one issue. ParaGUI requires
> libsigc++ 1.2 (>= 1.2.5) but the current libsigc package in Buildroot is for libsigc++ 2.2 (2.2.11).
> The API is quite different between the 1.2 and 2.2 versions. So to get paragui to compile I
> had to also add a libsigc1 package (leaving the current libsigc as-is).
>
> Is this acceptable? If so I can post 2 patches:
Yes, packaging libsigc1 separately is OK, since it has a different API
than libsigc.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-09 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 0:10 [Buildroot] ParaGUI package? Hartley Sweeten
2014-01-08 3:34 ` Thomas Petazzoni
2014-01-08 17:05 ` Hartley Sweeten
2014-01-09 17:01 ` Arnout Vandecappelle
2014-01-09 22:34 ` Thomas Petazzoni
2014-01-09 22:37 ` Hartley Sweeten
2014-01-09 23:01 ` Thomas Petazzoni [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=20140110070111.483dd1a9@skate \
--to=thomas.petazzoni@free-electrons.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