Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Leonel <cls@elaxys.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [Fwd: Re:  SDL_image, SDL_ttf & Co (libpng12.So bug)]
Date: Mon, 27 Nov 2006 11:22:43 -0200	[thread overview]
Message-ID: <456AE6A3.1020409@elaxys.com.br> (raw)
In-Reply-To: <456AE31F.9020200@elaxys.com.br>

Hi,

I was using buildroot version 20061111 and managed to
compile SDL_image including the following flags (LDFLAGS) for the
linker.

$(SDL_IMAGE_DIR)/.compiled: $(SDL_IMAGE_DIR)/.configured
	$(MAKE) LDFLAGS=$(STAGING_DIR)/lib/libpng12.so -C $(SDL_IMAGE_DIR)
	touch $(SDL_IMAGE_DIR)/.compiled

I checked the dependencies of the generated libSDL_image.so
file and it seemed OK, but I haven't tested it yet in
the target.


But then I changed to a newer buildroot version: 20061124
and the previous modification was not enough, other linker
errors appeared, regarding the host directfb library.

I had to change the sdl.mk for SDL adding the following line
to configure:
	--disable-video-directfb

(I am not using directfb, only the framebuffer)


I am now having problems compiling SDL_ttf ...


Regards,


> Hi,
> 
> I have tried an older Buildroot version (20060217) and SDL_image is compiling
> fine. uClibc version is the same (0.9.28) than on my "non working" Buildroot
> snapshot (20060908).
> 
> Claudio, which Buildroot version are you using ?
> 
> Does somebody from buildroot team working on the very similar
> DirectFB/libpng12.so bug (ID 959) has already found something ?
> 
> regards,
> Julien
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
> 

       reply	other threads:[~2006-11-27 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <456AE31F.9020200@elaxys.com.br>
2006-11-27 13:22 ` Claudio Leonel [this message]
2006-11-27 17:27   ` [Buildroot] [Fwd: Re: SDL_image, SDL_ttf & Co (libpng12.So bug)] julien.boibessot at free.fr
2006-11-29 11:14     ` Claudio Leonel
2006-11-29 15:38       ` julien.boibessot at free.fr

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=456AE6A3.1020409@elaxys.com.br \
    --to=cls@elaxys.com.br \
    --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