Hi,
Sorry for top posting I'm far from a pc for a few days.
The media_addon can't be changed if we care about gcc2 addons. Nonetheless
an app migh want to load the addon inside the server, it migh be a trouble.
The media_server should be ok but I don't see any gain in doing so which is
worth the trouble.
Ffmpeg instead has nothing to do with changing the media_server compiler.
It's loaded inside apps through libmedia so no way to make old gcc2 apps to
use the newer ffmpeg or we'd have still done it.
Once ffmpeg was loaded inside the media_server and apps would communicate
using ports, pulkomandy changed it for obvious performance and crashes
issues.
+1 for me too to dismiss x86 anyway.
Il 14/giu/2017 00:11, "Julian Harnath" <julian.harnath@xxxxxxxxxxxxxx> ha
scritto:
Hey,
On 14.06.2017 00:05, waddlesplash wrote:
Is there any reason we build app_server as GCC2? I don't think there
is any way that it's "binary compatible" with the BeOS app_server, so
we could just change our build configuration to use GCC5 when
compiling app_server. (And the kernel too, at this point...)
Yes, and media server, or at least the add-on server, was another
candidate discussed sometimes, to get a non-ancient ffmpeg version in our
media player. But if we start compiling all those core components with gcc5
in a gcc2h... then it starts sounding an awful lot like gcc5h, doesn't it?
:-)
Regards
Julian
