| 5 | | WPE is a WebKit port intended to allow embedders to create simple and performant systems based on Web platform technologies. It is designed with hardware acceleration in mind, leveraging common 3D graphics APIs for best performance. |
| | 5 | WPE WebKit is a WebKit port intended to allow embedders to create simple and performant systems based on Web platform technologies. It is designed with hardware acceleration in mind, leveraging common 3D graphics APIs for best performance. |
| | 6 | |
| | 7 | = Building WPE WebKit from a release tarball = |
| | 8 | |
| | 9 | You can build and install WPE WebKit from a release tarball the same as you would any other CMake module. The only trick is that you must pass the CMake option -DPORT=WPE. For example, to do a release build with debug info and install the result: |
| | 10 | |
| | 11 | {{{ |
| | 12 | $ cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja |
| | 13 | $ ninja |
| | 14 | $ sudo ninja install |
| | 15 | }}} |
| | 16 | |
| | 17 | If you want to build WPE WebKit for production use, you should stop reading here. The rest of the instructions on this page are only suitable for development and testing. |
| | 18 | |
| | 19 | = Building WPE WebKit from git = |
| | 20 | |
| | 21 | If you want to do development on WebKit itself, you'll need a git checkout. You'll also need to use our JHBuild moduleset to build several dependencies, as using other versions of dependencies may cause layout tests to fail. '''The following steps are suitable for WebKit development only, not for production builds. Our JHBuild moduleset does not receive security or bugfix updates and it is not suitable for any purpose other than development and running layout tests. Do not run against untrusted websites.''' |
