Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] problem building a SDL app with buildroot
Date: Thu, 8 Nov 2012 18:36:49 +0100	[thread overview]
Message-ID: <20121108183649.0cae75f1@skate> (raw)
In-Reply-To: <CAHXCMMJjaafke3POAv04fdK80L_DWguu+UdbDrah9HSYPfwf-g@mail.gmail.com>

Samuel,

On Thu, 8 Nov 2012 11:49:58 +0100, Samuel Martin wrote:

> As a quick fix, in your app *.mk file, you can try to add:
> <your app prefix>_CONF_OPT += -DSDL_CONFIG="$(STAGING_DIR)/usr/bin/sdl-config"
> 
> You don't have to change anything in the sdl-config from the staging
> area, it is already handled by the sdl package.
> 
> BTW, that an issue we are aware of, and we talked a bit about it
> during the last Buildroot Dev Days.
> We just need some time to work on and figure out the best way to fix this.

We indeed discussed it, but as far as I understood, there isn't really
another solution than what we're doing at the moment. Options we
discussed where:

 (1) Install those <foo>-config scripts in $(HOST_DIR)/usr/bin. This
 isn't possible as they would clash with other <foo>-config scripts
 installed by host packages.

 (2) Create a special directory, which is in the PATH passed when
 configuring/building packages, in which we would install those
 <foo>-config script. This works quite OK when those <foo>-config
 scripts are self-contained (which is the case most of the time), but
 not necessarily if they are more elaborate.

So in general, I think we said it wasn't really worth the effort, and
it was probably a lot better to work on moving packages to pkg-config
instead.

For example, in this case, Jeremy should rather use the pkg-config
files of SDL to discover the right compiler/linker flags. pkg-config is
very nicely integrated with CMake, it should even simplify the
CMakeLists.txt.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2012-11-08 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18ba4b30-2ac3-44e7-ae59-5ca40d8137b3@zimbra2.corp.accelance.fr>
2012-11-08 10:21 ` [Buildroot] problem building a SDL app with buildroot Jeremy Rosen
2012-11-08 10:49   ` Samuel Martin
2012-11-08 12:35     ` Jeremy Rosen
2012-11-08 17:36     ` Thomas Petazzoni [this message]
2012-11-09 16:36       ` Samuel Martin

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=20121108183649.0cae75f1@skate \
    --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