Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/directfb
Date: Thu, 9 Oct 2008 09:57:47 +0200	[thread overview]
Message-ID: <20081009075747.GA31080@mx.loc> (raw)
In-Reply-To: <d6cda7730810082206nd6cc641wbcf9f3e2f5513672@mail.gmail.com>

On Thu, Oct 09, 2008 at 02:06:58AM -0300, Thiago A. Corr?a wrote:
>Hi Peter,
>
>>  correa> +
>>  correa> +config BR2_PACKAGE_DIRECTFB_XSERVER
>>  correa> +        bool "build with X server backend"
>>
>> Doesn't this need to depend on the various X implementations
>> (E.G. BR2_PACKAGE_XORG || ..XORG7 || ..TINYX ?
>>
>
>I suppose it should, yes. Sorry, I didn't notice.
>Btw, we really need a better check for X. something like the linux
>kernel with BR2_HAS_X that is set on either X implementation.
>XORG for instance is an empty folder in package/xorg. When/if that
>changes, we need to revisit all packages, quite anoying.

That's the reason why we have BR2_PACKAGE_XSERVER_none; See
package/Config.in
>
>>  correa> +config BR2_PACKAGE_DIRECTFB_PNG
>>  correa> +        bool "enable PNG support"
>>  correa> +        default y
>>  correa> +        depends on BR2_PACKAGE_DIRECTFB
>>  correa> +      select BR2_PACKAGE_LIBPNG
>>  correa> +      select BR2_PACKAGE_ZLIB
>>
>> Indentation seems wrong. Actually it's right here and wrong everywhere
>> else. Config.in uses tabs for indentation, not spaces (and help text
>> is tab+2 spaces).
>>
>
>Unfortunally I can't see that using vi. Since it's not Python, I
>honestly don't see the space/tab being relevant.

It is relevant since it is the style that is perused in this project.
Try something like :match Error '\(^\s\(\s\s\)[^[:alnum:]]\|\s\+$\)'
you get the idea..
>
>>  correa> +config BR2_PACKAGE_DIRECTFB_GIF
>>  correa> +        bool "enable GIF support"

Can you please strip all "enable" and "compile" off those bools. They
are highly redundant.

TIA

  reply	other threads:[~2008-10-09  7:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 20:29 [Buildroot] svn commit: trunk/buildroot/package/directfb correa at uclibc.org
2008-10-08 18:36 ` Peter Korsgaard
2008-10-09  5:06   ` Thiago A. Corrêa
2008-10-09  7:57     ` Bernhard Reutner-Fischer [this message]
2008-10-09  1:25 ` Ormund Williams
2008-10-09  5:21   ` Thiago A. Corrêa
2008-10-09 12:42     ` Ormund Williams
2008-10-09 12:51       ` Peter Korsgaard
2008-10-09 13:11         ` Ormund Williams
2008-10-11  4:19       ` Ormund Williams
  -- strict thread matches above, loose matches on Subject: below --
2009-01-21 19:20 jacmet at uclibc.org
2009-01-21 19:20 jacmet at uclibc.org
2009-01-21 15:49 jacmet at uclibc.org
2009-01-11 20:35 ulf at uclibc.org
2008-10-09 18:36 correa at uclibc.org
2008-10-09 18:36 correa at uclibc.org
2008-10-09  5:06 correa at uclibc.org
2008-10-09  9:45 ` Peter Korsgaard
2008-04-01  6:51 jacmet at uclibc.org
2007-11-16 16:10 vanokuten at uclibc.org
2007-09-12  5:20 ulf at uclibc.org
2007-09-05  6:49 ulf at uclibc.org
2007-08-13  6:14 ulf at uclibc.org
2007-08-12 23:30 ulf at uclibc.org
2007-08-12 18:21 ulf at uclibc.org
2007-08-12 14:40 ulf at uclibc.org
2007-08-11 21:53 ulf at uclibc.org
2007-06-26  6:24 aldot at uclibc.org
2007-02-02 12:41 jacmet at uclibc.org

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=20081009075747.GA31080@mx.loc \
    --to=rep.dot.nop@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