[openal] Further consideration of C++

[Daniel Gibson]

On 25.10.2018 14:03, Chris Robinson wrote:
> When the switch to C++ was discussed some years ago, the concern was 
> brought up that for binary apps on Linux, there could be conflicts if 
> the system OpenAL relied on the system libstdc++, while the app itself 
> is linked to an app-provided libstdc++. This would cause a problem 
> because the app-provided libstdc++ can be older, so some symbols the 
> system OpenAL may rely on would be missing. There are ways to work 
> around this, but it's less than ideal if the user has to manually fiddle 
> with files to get an app to run.

I don't think this is very relevant.
There are other system libs, like Mesa's libGL (used by everyone except 
for nvidia users that use their proprietary drivers) that also link 
libstdc++ and thus have the same problem.
Bundling libstdc++ with your app and unconditionally using the bundled 
version is just a bad idea and leads to trouble.
(If they absolutely need to bundle a libstdc++, they need to check if 
the system's version is older than the bundled version and only then use 
the bundled version)

Cheers,
Daniel