From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ParaGUI package?
Date: Wed, 8 Jan 2014 11:34:04 +0800 [thread overview]
Message-ID: <20140108113404.413a4685@skate> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D8817E678D7@P3PWEX4MB008.ex4.secureserver.net>
Dear Hartley Sweeten,
On Wed, 8 Jan 2014 00:10:29 +0000, Hartley Sweeten wrote:
> I'm trying to find a simple GUI library that can be used with SDL and this one appears
> to cover my needs. Unfortunately the ParaGUI library appears to be a bit dead. The
> latest release at http://download.savannah.gnu.org/releases/paragui/ is
>
> paragui-1.1.8.tar.gz 19-Oct-2004
>
> I found a newer branch on https://github.com/pipelka/paragui that appears to be
> version 1.1.11.
My first reaction is: do you really want to start using something that
appears to be dead/deprecated?
> Makefile.am: error: required file './NEWS' not found
> Makefile.am: error: required file './ChangeLog' not found
These seems to be the real problems. Easiest solution is to add a post
patch hook with "touch $(@D)/NEWS $(@D)/ChangeLog"
A cleaner solution is to add the "foreign" option in the
AM_INIT_AUTOMAKE call in configure.in, like:
AM_INIT_AUTOMAKE([1.10 no-define foreign])
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-08 3:34 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 [this message]
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
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=20140108113404.413a4685@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