[DO NOT MERGE] Temporary hack to build using custom CEF build

[perlun]

The idea here is to let me build highly experimental CEF NuGet packages, which provides the proprietary codecs.

I spent the weekend (yes, literally; it took many hours to set up the build environment and wait for 30000 files to compile...) building a custom version of CEF with proprietary codecs enabled, for those willing to take the legal risk of using them.

The packages are here now:

https://www.myget.org/feed/perlun/package/nuget/cef.sdk
https://www.myget.org/feed/perlun/package/nuget/cef.redist.x86

(x86 only for now, since linking failed with an out-of-memory error after about an hour or so waiting to link libcef.dll in the x64 target.)

This serves as an intermediate solution while we wait for CEF 63 64 (unfortunately), which will include (some) of the proprietary codecs which are now considered "safe" to use from a legal/patent perspective. More details: cefsharp/CefSharp#1479

[AppVeyorBot]

❌ Build cef-binary 62.0.0-CI30 failed (commit fb2d2bf232 by @perlun)

[perlun]

This page hosts my custom build of CEF.

[amaitland]

Please remove or update the package links as per our previous discussions, thank you.

[perlun]

Please remove or update the package links as per our previous discussions, thank you.

Thanks @amaitland for the reminder! Sorry for not having fixed it already. I've now pointed these links to go to the updated, unofficial packages.

Once again reminding anyone using this: you take the full risk yourself for any legal consequences; this is a "gray zone" which is clearly illegal in some countries and "possibly legal" in others. I am not a lawyer, so please consult legal help if in doubt.

[perlun]

I will close this now. Will retain the branch in my personal fork if anyone needs it: https://github.com/perlun/cef-binary/tree/perlun/proprietary-codecs-experiment