Turns out webkit requires some more tools than what is available as pre-compiled windows binaries. Bison and gprof are required and still available, but \"flex\" is required in version 2.5.33 whereas the latest windows binary of it on gnuwin32 is 2.5.4. As Phil already wrote, because of this it is most probably easier to cross-compile on a Linux box with the mingw32 cross compile toolchain.
For Windows, bison, flex and gperf are provided with the source code at c:\\pathToQt\\gnuwin32\\bin. Get Ruby from You can download the precompiled ICU packages from download.qt.io, or see Compiling-ICU to compile your own.
Qt 5 can make use of the ICU library for UNICODE and Localization support. This is required for building Qt WebKit. You can use pre-compiled versions of ICU with a Visual Studio 2010 dependency from the website, get pre-compiled versions for different compilers from download.qt.io, or compile ICU on your own.
If pip is not able to find a binary wheel file that matches your platformand your version of Python, then it will download the source archive andwill attempt to build it for you. If you have the required compiler anddependent libraries installed, then this will be a feasible approach foryou, although it can take some time to do the build. The end result will bethe same as if there was a binary wheel available for you. In fact, pip canalso be told to just build the wheel and not do the install. This way youcan reuse the wheel file for different Python environments or on othermachines, or whatever, without needing to rebuild for each one.
Linux - (Tested with Ubuntu **.04 and 20.04) Install dependencies: sudo apt-get update && sudo apt-get install libgtk-3-dev libwebkit2gtk-4.0-dev. To compile, run gcc -std=c++11 -shared -DOS_LINUX Exports.cpp Photino.Linux.cpp -o x64/$(buildConfiguration)/Photino.Native.so 'pkg-config --cflags --libs gtk+-3.0 webkit2gtk-4.0' -fPIC
Let's take a PC. I build my own, put my own software on it, do as I like. THIS IS THE RASPBERRY PI! It comes with a slot for an SD card or whatever, which you use as your hard disk, and you have FULL CONTROL over it. What goes on the raspberry pi's \"hard drive\" is fully under the owner's control.Then you get locked systems. My wife's just acquired a Google Nexus 7. I'm not going to bother rooting it, but the point is that it is not easy to access its \"hard drive\" and change the OS or stuff like that. Would you call a Nexus 7 embedded To my mind it's far closer to embedded than the Pi!Then there's what most people consider embedded systems. That come, for all intents and purposes, with the software hard-coded in ROM.By my definitions, an embedded system is perfectly okay with the GPL - no-one can update the software, so there's no problem.Equally, an open system is perfectly okay. Whether it's a PC or a Raspberry Pi, the user has FULL ACCESS to the hard drive or equivalent, so can update things as they please.It's the things in the middle, like the Nexus 7, that are the problem. If I can download apps, and get access to the source, then that's fine with GPL2. If I can cross-compile the source and replace the original version of the app with my version that's okay with GPL3 too. That's probably possible with the Nexus. It's probably NOT possible with the iPad.And that is the crux of the problem with these locked systems. The LGPL requires that you have the ability to modify PART of the app. So if you can't replace the LGPL library (like you probably can't on an iPad), then the LGPL is useless for iPad apps.I think the troub