rivolt80 wrote:Maybe the maintainers could shed some light. Hello awesome people. Can we build JCEF with proprietary codecs? If yes, what would be the procedure?
magreenblatt wrote:rivolt80 wrote:Maybe the maintainers could shed some light. Hello awesome people. Can we build JCEF with proprietary codecs? If yes, what would be the procedure?
Yes, you can.
1. Build CEF locally with proprietary codecs enabled as described above.
2. Create a CEF binary distribution from your local build.
3. Modify the JCEF top-level CMakeLists.txt file to use your locally created binary distribution (set CEF_VERSION, and copy the binary distribution folder to the third_party/cef directory).
magreenblatt wrote:rivolt80 wrote:Maybe the maintainers could shed some light. Hello awesome people. Can we build JCEF with proprietary codecs? If yes, what would be the procedure?
Yes, you can.
1. Build CEF locally with proprietary codecs enabled as described above.
2. Create a CEF binary distribution from your local build.
3. Modify the JCEF top-level CMakeLists.txt file to use your locally created binary distribution (set CEF_VERSION, and copy the binary distribution folder to the third_party/cef directory).
D:\CEF\chromium_git\chromium\src>ninja -C out\Debug_GN_x64 cef
ninja: Entering directory `out\Debug_GN_x64'
[1/5] LINK(DLL) libcef.dll libcef.dll.lib libcef.dll.pdb
FAILED: libcef.dll libcef.dll.lib libcef.dll.pdb
ninja -t msvc -e environment.x64 -- ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /IMPLIB:./libcef.dll.lib /DLL /OUT:./libcef.dll /PDB:./libcef.dll.pdb @./libcef.dll.rsp
Failure value returned from cantFail wrapped call
UNREACHABLE executed at C:\b\rr\tmpswcnjy\w\src\third_party\llvm\include\llvm/Support/Error.h:707!
Stack dump:
0. Program arguments: ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /IMPLIB:./libcef.dll.lib /DLL /OUT:./libcef.dll /PDB:./libcef.dll.pdb @./libcef.dll.rsp
#0 0x00007ff761c23846 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x13846)
#1 0x00007ff763d2741c (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x211741c)
#2 0x00007ff763d22368 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x2112368)
#3 0x00007ff761c2a7e7 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1a7e7)
#4 0x00007ff763acb576 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1ebb576)
#5 0x00007ff763ac86a4 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1eb86a4)
#6 0x00007ff761f53f58 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x343f58)
#7 0x00007ff761ccc638 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xbc638)
#8 0x00007ff761cb94f8 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xa94f8)
#9 0x00007ff761cb247d (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xa247d)
#10 0x00007ff761c78c30 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x68c30)
#11 0x00007ff761c6f511 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x5f511)
#12 0x00007ff761c1143e (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x143e)
#13 0x00007ff763cfa2f4 (D:\CEF\chromium_git\chromium\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x20ea2f4)
#14 0x00007ffd6b631fe4 (C:\WINDOWS\System32\KERNEL32.DLL+0x11fe4)
#15 0x00007ffd6c32f061 (C:\WINDOWS\SYSTEM32\ntdll.dll+0x6f061)
ninja: build stopped: subcommand failed.
Users browsing this forum: No registered users and 59 guests