huh, that's a good point pity I've never gotten around to contributing anything to either webkit or chromium upstream
-
-
Replying to @11rcombs
It also statically links ffmpeg. Not totally obvious, because the version strings get optimized out, but it's definitely in there. $ strings chrome|grep -i ffmpeg, Not yet implemented in FFmpeg, patches welcome (see libavutil/error.c)
1 reply 0 retweets 3 likes -
They USED to dynamically link these things (e.g. ffmpegsumo.dll)... interesting.
1 reply 0 retweets 0 likes -
Replying to @daemon404 @11rcombs
The fuck. There's a string in the official Chrome binary from a file with a huge LGPLv2.1 header (at least, probably zillions more). Does Google Legal know something we don't about the LGPL, or are they just incompetent?
1 reply 0 retweets 0 likes -
Looking at the file that has Blink and FFmpeg linked (chrome_child.dll on Windows, anyway), I'm not sure it actually contains anything that isn't reproducible with the Chromium source?
1 reply 0 retweets 0 likes -
Replying to @daemon404 @11rcombs
That's possible. On Linux it's the main chrome binary. That's why I asked in the OP if that entire file was reproducible from Chromium source.
1 reply 0 retweets 0 likes -
I'm not sure what's not in Chromium anymore. Flash is delayloaded/downloaded (via pepper + updater), and that code is OSS - not sure what else they could be linking to make it unreproducible? Telemetry is also the same.
1 reply 0 retweets 0 likes -
Replying to @daemon404 @11rcombs
I guess the logos and such, but that's in resource files probably? I'm just wondering if there's anything code-wise that is different about Chrome, other than bundling plugins (like widevine, but that's a solib)...
1 reply 0 retweets 0 likes -
You'd have to RE it or ask the Chrome guys, I guess.
1 reply 0 retweets 0 likes
Replying to @daemon404 @11rcombs
Well, given the license requirement to be able to replace the LGPLed parts, the onus is kind of on *them* to document how to do so to be in compliance :-)
8:22 AM - 7 Aug 2018
0 replies
0 retweets
1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.