From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] SDL2_ttf requires libpng12 but Buildroot installs libpng16
Date: Thu, 12 May 2016 23:45:48 +0200 [thread overview]
Message-ID: <20160512234548.20d6cd28@free-electrons.com> (raw)
In-Reply-To: <CAGrGpJB1XFuZWdXS7rWeaA9E7N2yzde8JuSp_A8KjU2vD6h_VA@mail.gmail.com>
Hello,
On Thu, 12 May 2016 13:05:56 -0600, Peter Thompson wrote:
> Below are my personal notes on how I compiled the SDL2 suite - in the
> hopes it is helpful to someone else. pmtstaging is a copy of the
> buildroot sysroot which I wanted to keep pristine during this process.
>
> I will try to convert these notes into a buildroot patch and submit it -
> making life much easier in the future.
Quick question that might sound silly, but I believe worth asking: why
are you taking this terribly complicated path to build SDL2_ttf
manually, rather than creating a Buildroot package directly?
The Buildroot autotools package infrastructure already handles most of
the cross-compilation problems by itself. So all this terrible dance of
CFLAGS and LDFLAGS, copying of sysroot and stuff that you're doing
would have been completely unneeded if you had done a Buildroot package
from the beginning.
It seems to me like you've wasted a huge amount of time :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-12 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 19:05 [Buildroot] SDL2_ttf requires libpng12 but Buildroot installs libpng16 Peter Thompson
2016-05-12 21:45 ` Thomas Petazzoni [this message]
2016-05-13 20:39 ` Peter Thompson
2016-05-13 20:44 ` Thomas Petazzoni
2016-05-13 20:55 ` Peter Thompson
-- strict thread matches above, loose matches on Subject: below --
2016-05-02 15:57 Peter Thompson
2016-05-02 16:14 ` Gustavo Zacarias
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=20160512234548.20d6cd28@free-electrons.com \
--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