From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] SDL directfb dependence [was: Re: svn commit: trunk/buildroot/package/sdl]
Date: Fri, 27 Jul 2007 18:16:20 +0200 [thread overview]
Message-ID: <20070727161620.GD25147@aon.at> (raw)
In-Reply-To: <00a401c7cf52$629f3f60$dcc4af0a@atmel.com>
On Thu, Jul 26, 2007 at 08:55:57AM +0200, Ulf Samuelsson wrote:
>>> The SDL compile failed since "directfb.h" could not be found
>>> so I made the assumption, that it was neccessary.
>>> Maybe I was wrong, but if it is not required, why the error message?
>>>
>>>
>>> > If you want directfb and directfb-support, the you should select it
>>> > manually, no?
>>>
>>> Best Regards
>>> Ulf Samuelsson
>>>
>
>> DirectFB is not required.
>> SDL only needs the directfb.h header to build, in case directfb might be
>> invoked later at run time.
>> directfb is not used by default by SDL
>>
>>
>> -Rex
>>
>
>OK, so we need to download the DirectFB and install its headers.
>SDL won't build in buildroot, unless we do.
Can you check if a
ifndef ($(BR2_PACKAGE_DIRECTFB),y)
$(SED) "/directfb.h>/d" all/odd/files/*
endif
in the configure stage bypasses this odd dependency?
I.e. if we (or rather the SDL folks) don't need some structs from
directfb then we can wipe the header just fine.
Apart from that, isn't there a --disable-directfb or something like
that in SDL?
/me pets GGI
next prev parent reply other threads:[~2007-07-27 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 17:39 [Buildroot] svn commit: trunk/buildroot/package/sdl ulf at uclibc.org
2007-07-25 22:39 ` Bernhard Fischer
2007-07-25 23:47 ` Ulf Samuelsson
2007-07-26 1:06 ` Rex Ashbaugh
2007-07-26 6:55 ` Ulf Samuelsson
2007-07-27 16:16 ` Bernhard Fischer [this message]
2007-07-27 17:38 ` [Buildroot] SDL directfb dependence [was: Re: svn commit: trunk/buildroot/package/sdl] Ulf Samuelsson
2007-07-27 18:00 ` Bernhard Fischer
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=20070727161620.GD25147@aon.at \
--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