From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/3] chocolate-doom: new package
Date: Thu, 24 Dec 2015 08:29:21 +0100 [thread overview]
Message-ID: <20151224082921.1e482c18@free-electrons.com> (raw)
In-Reply-To: <CABLs7GUV97Ck5V6_vgmsCJfgxgvgZkkrvKvLeV8RX3RZK9+6Ug@mail.gmail.com>
Dear Rodrigo Rebello,
On Wed, 23 Dec 2015 22:33:01 -0200, Rodrigo Rebello wrote:
> Agreed. I have considered exactly that when I was working on the
> patch, but I have decided to leave it for later since a patch for
> SDL_mixer is also necessary (SDL_mixer.pc is missing a 'Libs.private'
> section with libraries necessary for static linking). I've just had a
> look at it and the solution is actually quite simple, so I'll work on
> it and propose a patch. That will also be useful to fix a recent ltris
> autobuild failure related to static linking as well.
Indeed, according to your description of the problem, it is really
SDL_mixer.pc that needs to be fixed. However, if I looked correctly,
chocolate-doom doesn't use pkg-config to find libraries, so it would
have to be changed as well.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-12-24 7:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 19:47 [Buildroot] [PATCH v4 1/3] chocolate-doom: new package Rodrigo Rebello
2015-11-06 19:47 ` [Buildroot] [PATCH v4 2/3] doom-wad: bump to version 1.9 Rodrigo Rebello
2015-12-23 22:37 ` Thomas Petazzoni
2015-12-23 23:59 ` Rodrigo Rebello
2015-12-24 7:28 ` Thomas Petazzoni
2015-11-06 19:47 ` [Buildroot] [PATCH v4 3/3] doom-wad: add BR2_PACKAGE_CHOCOLATE_DOOM as alternate dependency Rodrigo Rebello
2015-12-23 22:35 ` Thomas Petazzoni
2015-12-23 22:34 ` [Buildroot] [PATCH v4 1/3] chocolate-doom: new package Thomas Petazzoni
2015-12-24 0:33 ` Rodrigo Rebello
2015-12-24 7:29 ` Thomas Petazzoni [this message]
2015-12-24 11:11 ` Rodrigo Rebello
2016-02-21 16:23 ` Romain Naour
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=20151224082921.1e482c18@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.