From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] SDL2+directfb combo does not work as built by buildroot-2018.02.3
Date: Tue, 28 Aug 2018 16:35:55 +0200 [thread overview]
Message-ID: <87a7p65zjo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAGrGpJCe67xHWAceYw6-oD=iPoL0be8-ZhRgmWfhQRuG0GwxeA@mail.gmail.com> (Peter Thompson's message of "Tue, 28 Aug 2018 08:17:33 -0600")
>>>>> "Peter" == Peter Thompson <peter.macleod.thompson@gmail.com> writes:
> Hi Peter
> My original plan was to wait for the next SDL2 release thereby allowing
> SDL2 to fix itself before updating the SDL2_VERSION in buildroot.
> Otherwise we have to change buildroot SDL2_VERSION to point to the
> temporary patched SDL2 source for download:
> http://www.libsdl.org/tmp/SDL-2.0.zip
> OR
> somehow change buildroot to download this patch and apply it to the
> downloaded SDL2-2.0.8 before compiling (I am not sure how to do this in
> buildroot).
.. Or simply include the hg commit as a .patch file in the package.
> Then we would need to re-change this all back when the new release of SDL2
> incorporates this patch.
Correct.
Do you know when sdl2-2.0.9 is planned? 2.0.8 is what we are using both
for 2018.02 (the current long term support version), 2018.05 (the
current release) and master (what will very soon become 2018.08).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-08-28 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 11:11 [Buildroot] SDL2+directfb combo does not work as built by buildroot-2018.02.3 Peter Thompson
2018-08-28 2:11 ` Peter Thompson
2018-08-28 8:15 ` Peter Korsgaard
2018-08-28 14:17 ` Peter Thompson
2018-08-28 14:35 ` Peter Korsgaard [this message]
2018-08-28 16:56 ` Peter Thompson
2018-08-29 9:21 ` Peter Thompson
2018-08-29 13:39 ` Peter Korsgaard
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=87a7p65zjo.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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