Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Schoenert <c.schoenert@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] directfb: bumping version to 1.6.3
Date: Tue, 02 Apr 2013 23:56:28 +0200	[thread overview]
Message-ID: <515B540C.6070905@googlemail.com> (raw)
In-Reply-To: <20130321201352.6b9455c2@skate>

Hello Thomas, Hello Arnout,

Am 21.03.2013 20:13, schrieb Thomas Petazzoni:
> No, I think Arnout means that we should leave as few options
> "automatically" detected as possible.
> 
> For example, we really like to have:
> 
> ifeq ($(BR2_PACKAGE_FOO_FEATURE_BAR),y)
> FOO_CONF_OPT += --enable-bar
> else
> FOO_CONF_OPT += --disable-bar
> endif
> 
> and for all options that are not explicitly --enable-<bleh> somewhere,
> have a global:
> 
> FOO_CONF_OPT += \
> 	--disable-<bleh> \
> 	--disable-<blah>
> 
> this avoids the configure script from automatically detecting things on
> the host machine that we don't want it to detect.

some little status info on that.
The last days I worked on the "new" Config.in and the directfb.mk
Makefile with your suggestions. Until now I would say the most options
are implemented and I can also build the most of them.
But I found some issues inside the directfb archive (missing headers :)
and some code errors). I found one patch to fix the code errors and cook
one other to fix a configure problem, but the missing headers are just
to fix if the package would switch to a git checkout.

I wrote up to upstream to fix the header and the code error. I will wait
for response and in the between time I will more clean up my current
work. Some of the new options have new dependencies like libsvg-cairo,
linotyp, mng or jasper for jpeg2000. The libsvg-cairo package I will try
to implement if I find some free time for it, the other dependencies
have to find some other person. ;)

Regards
Carsten

  reply	other threads:[~2013-04-02 21:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-10  9:47 [Buildroot] [PATCH 0/0] Updating directfb and divine Carsten Schoenert
2013-03-10  9:47 ` [Buildroot] [PATCH 1/4] directfb: bumping version to 1.6.3 Carsten Schoenert
2013-03-10 10:32   ` Thomas Petazzoni
2013-03-10 12:34     ` Carsten Schoenert
2013-03-17 13:59       ` Carsten Schoenert
2013-03-21  6:56         ` Arnout Vandecappelle
2013-03-21 18:06           ` Carsten Schoenert
2013-03-21 19:13             ` Thomas Petazzoni
2013-04-02 21:56               ` Carsten Schoenert [this message]
2013-03-10 16:50     ` Carsten Schoenert
2013-03-10 17:25       ` Thomas Petazzoni
2013-03-10  9:47 ` [Buildroot] [PATCH 2/4] divine: " Carsten Schoenert
2013-03-10  9:47 ` [Buildroot] [PATCH 3/4] directfb: expanding the help strings Carsten Schoenert
2013-03-10 10:27   ` Thomas Petazzoni
2013-03-10 12:21     ` Carsten Schoenert
2013-03-10 13:13       ` Thomas Petazzoni
2013-03-10  9:47 ` [Buildroot] [PATCH 4/4] directfb: fixing typo in variables Carsten Schoenert
2013-03-10 10:25   ` Thomas Petazzoni
2013-03-10 12:23     ` Carsten Schoenert

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=515B540C.6070905@googlemail.com \
    --to=c.schoenert@gmail.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