From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/sdl2: Fix Raspberry Pi support in package SDL2
Date: Thu, 18 Jan 2018 16:05:14 +0100 [thread overview]
Message-ID: <20180118160514.0684a720@windsurf.lan> (raw)
In-Reply-To: <20180118081528.16612-1-g@maral.me>
Hello,
Thanks for respining! It looks much better, but there's still one thing
I'm not sure is very good. See below.
On Thu, 18 Jan 2018 00:15:28 -0800, Guillermo A. Amaral wrote:
> ++#if SDL_VIDEO_DRIVER_RPI
> ++ path = SDL_getenv("LD_LIBRARY_PATH");
> ++ if (path) {
> ++ const int path_size = SDL_strlen(path) + 1 + sizeof(g_rpi_opt_path);
> ++ char *new_path = SDL_calloc(1, path_size);
> ++ strcat(new_path, path);
> ++ strcat(new_path, ":");
> ++ strcat(new_path, g_rpi_opt_path);
> ++ SDL_setenv("LD_LIBRARY_PATH", new_path, 1);
> ++ SDL_free(new_path);
> ++ } else {
> ++ SDL_setenv("LD_LIBRARY_PATH", g_rpi_opt_path, 1);
> ++ }
> ++ path = NULL;
Yerk, upstream has accepted this? To me, it looks really terrible to
set LD_LIBRARY_PATH from within a program. Is it really considered a
good practice ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-18 15:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 3:34 [Buildroot] [PATCH 1/2] package/sdl2: Fix Raspberry Pi support for SDL2 Guillermo A. Amaral
2018-01-16 3:34 ` [Buildroot] [PATCH 2/2] package/rpi-fbcp: Added package for Raspberry Pi Guillermo A. Amaral
2018-01-16 8:26 ` Thomas Petazzoni
2018-01-16 18:05 ` Guillermo A. Amaral
2018-01-16 8:23 ` [Buildroot] [PATCH 1/2] package/sdl2: Fix Raspberry Pi support for SDL2 Thomas Petazzoni
2018-01-16 17:50 ` Guillermo A. Amaral
2018-01-18 8:15 ` [Buildroot] [PATCH 1/1] package/sdl2: Fix Raspberry Pi support in package SDL2 Guillermo A. Amaral
2018-01-18 8:19 ` Guillermo A. Amaral
2018-01-18 15:05 ` Thomas Petazzoni [this message]
2018-01-18 15:44 ` Adrian Perez de Castro
2018-01-18 16:22 ` Thomas Petazzoni
2018-01-18 16:35 ` Guillermo A. Amaral
2018-01-18 16:43 ` Thomas Petazzoni
2018-01-18 17:54 ` [Buildroot] [PATCH 1/1] package/sdl2: Fix Raspberry Pi support for SDL2 Guillermo A. Amaral
2018-01-18 17:56 ` Guillermo A. Amaral
2018-01-18 21:17 ` Thomas Petazzoni
2018-01-19 6:25 ` Guillermo A. Amaral
2018-01-19 17:11 ` Ryan Coe
[not found] ` <CAPeEpDouAm5vqoQQ3PmHcJwvssMe=3yyyrQUvc4zoaw3ehandw@mail.gmail.com>
[not found] ` <CAPeEpDrdRC2eDW5Q=YEc8naVfNz6aLq7zbd4Wcx=FUmEmfdswQ@mail.gmail.com>
[not found] ` <CAPeEpDqrw8369-bhX0j3+5T-ZWo_1bW6=tnYpw8SiWUj5KMBAQ@mail.gmail.com>
[not found] ` <CAPeEpDoZ64=_wE=4OXQvZ_hJdZN9u7eAzOEbXP-+bH05dF1WGg@mail.gmail.com>
2018-01-19 19:24 ` Guillermo Amaral
2018-01-19 21:40 ` Peter Korsgaard
2018-01-20 21:25 ` [Buildroot] [PATCH 1/1] package/sdl2: Remove trailing backslash Guillermo A. Amaral
2018-01-22 21:29 ` 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=20180118160514.0684a720@windsurf.lan \
--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