[Scummvm-devel] Cross-Compiling issues

[Andre Heider]

On Sat, May 7, 2011 at 7:46 PM, Klaus Reimer <k at ailis.de> wrote:
> On 05/07/2011 06:43 PM, John Willis wrote:
>> __bswapsi2 is in libgcc.so,
>
> Using "-static-libgcc" fixes the problem. I'm not quite sure if this is
> a good solution after reading this in the documentation:
>
> "There are several situations in which an application should use the
> shared libgcc instead of the static version. The most common of these is
> when the application wishes to throw and catch exceptions across
> different shared libraries. In that case, each of the libraries as well
> as the application itself should use the shared libgcc."
>
> So does it break some error handling in the plugins when I use the
> "-static-libgcc" option? For Info: The mips-sgi platform also uses this
> option.

using the libgcc/libstdc++ versions which ship with webos v1 devices
has advantages. most likely every binary on the device depends on
libgcc, and alot on libstdc++. the system only needs to map its
text/rodata sections once into memory and can share it for all
processes. it also reduces the size of the webos scummvm package.
you could try to move -sysroot from LDFLAGS to CXXFLAGS, since its
also relevant for include paths. i don't recall if that might get rid
of the bswap dependency.
if not, shipping the two libs is your best option. but if its really
just to avoid a false positive warning, it doesn't sound like it's
worth it.

Regards,
Andre