QtWebEngine --register-pepper-plugins
-
Just make sure you use the same Chromium version that is bundled with Qt (61, 62, now 65 with the alpha)
I drop the dll or the dylib right near the the executable after compilation -
@maximus Hello, can you describe it in detail?
Here's the thing: I put the plugin's DLL, lib in the release, and "don't support the plugin";Did you rebuild Qt from source with the flag on?
aka:
git clone qt5 cd qt5 git checkout tag version, i.e : git checkout v5.10.0 perl init-repository --configure, use another folder prefix on the same level as qt source ./configure -opensource -confirm-license -release -webengine-pepper-plugins -webengine-proprietary-codecs -no-openssl -securetransport -prefix /Users/maxime.blais/Qt/Qt5.11.0_alpha make make install -
Did you rebuild Qt from source with the flag on?
aka:
git clone qt5 cd qt5 git checkout tag version, i.e : git checkout v5.10.0 perl init-repository --configure, use another folder prefix on the same level as qt source ./configure -opensource -confirm-license -release -webengine-pepper-plugins -webengine-proprietary-codecs -no-openssl -securetransport -prefix /Users/maxime.blais/Qt/Qt5.11.0_alpha make make install -
This is the parameter I compile.
Qt WebEngine:
Embedded build ......................... no
Pepper Plugins ......................... yes
Printing and PDF ....................... yes
Proprietary Codecs ..................... yes
Spellchecker ........................... yes
WebRTC ................................. yes
Using system ninja ..................... yes -
This is the parameter I compile.
Qt WebEngine:
Embedded build ......................... no
Pepper Plugins ......................... yes
Printing and PDF ....................... yes
Proprietary Codecs ..................... yes
Spellchecker ........................... yes
WebRTC ................................. yes
Using system ninja ..................... yesThis is looking good.
Where did you get the plugin ddl from?
Make sure it is from the same Chromium version as the Qt version you are using (Chromium 56, x86 or x64)
Kind of hard to find old version of widevine.dll so I prefered to go with the alpha version, which is using latest Chromium 65 -
This is looking good.
Where did you get the plugin ddl from?
Make sure it is from the same Chromium version as the Qt version you are using (Chromium 56, x86 or x64)
Kind of hard to find old version of widevine.dll so I prefered to go with the alpha version, which is using latest Chromium 65@maximus !
My source code uses the official google example. My dll and lib are compiled by using vs2013.
Figure 1 below shows the pepper plugins that I loaded on chrome version 64.
Figure 2, I use Qt official Examples "simplebrowser.pro", but did not load the pepper plugins.
-
This is looking good.
Where did you get the plugin ddl from?
Make sure it is from the same Chromium version as the Qt version you are using (Chromium 56, x86 or x64)
Kind of hard to find old version of widevine.dll so I prefered to go with the alpha version, which is using latest Chromium 65 -
This is looking good.
Where did you get the plugin ddl from?
Make sure it is from the same Chromium version as the Qt version you are using (Chromium 56, x86 or x64)
Kind of hard to find old version of widevine.dll so I prefered to go with the alpha version, which is using latest Chromium 65First of all, thank you very much for your reply. Moreover, I hope that you will give me a clear explanation of your solution to this problem. We should have a time difference of 12 hours. We cannot communicate in time. I hope you will speak more of your opinion.
-
This is looking good.
Where did you get the plugin ddl from?
Make sure it is from the same Chromium version as the Qt version you are using (Chromium 56, x86 or x64)
Kind of hard to find old version of widevine.dll so I prefered to go with the alpha version, which is using latest Chromium 65
