lvsti / Cef.swift
Programming Languages
Labels
Projects that are alternatives of or similar to Cef.swift
CEF.swift
Swift bindings for the Chromium Embedded Framework.
Requirements
Xcode 10.1, Swift 4.2 (see notes below)
Supported target platforms: macOS 10.9+
Required tools: jq, xcpretty, lxml
To set up your environment:
$ brew install jq
$ gem install xcpretty
$ pip install lxml
How to build
The easy way
You can now build CEF.swift using Carthage. Just add the following line to your Cartfile
:
github "lvsti/CEF.swift" "<branch_specifier>"
(For the branch_specifier
, see the notes on branches below.)
Note that the bootstrap build will take quite some time as CEF.swift has to fetch and build external dependencies as well.
The oldschool way
- fetch this repo
- switch to the appropriate branch in CEF.swift to match the CEF distribution (see notes below)
- run
scripts/setup.sh
from the repo root - now you are ready to compile the CEF.swift framework
CEF branches
CEF is developed on multiple branches simultaneously, which differ in API and functionality (see Spotify OpenSource and ChromeStatus). CEF.swift aims at supporting the current stable release branch and a couple more of earlier releases. For any CEF branch NNNN
, the corresponding CEF.swift branch is named cef_NNNN
.
Currently supported branches:
- 3809 (Chrome 76) - Swift 4.2
- 3770 (Chrome 75) - Swift 4.2
- 3729 (Chrome 74) - Swift 4.2
- 3683 (Chrome 73) - Swift 4.2
- 3626 (Chrome 72) - Swift 4.2
- 3578 (Chrome 71) - Swift 4.2
- 3538 (Chrome 70) - Swift 4.2
Archived branches (not maintained anymore):
- 3497, 3440, 3396, 3359, 3325, 3282, 3239, 3202, 3163 - Swift 4.1
- 3112, 3071, 3029, 2987, 2924, 2883, 2840, 2785, 2743, 2704 - Swift 3.0
- 2623, 2526, 2454, 2357 - Swift 2.3
Getting started
Check out the (pretty skinny) CEFDemo app under Samples/CEFDemo
to get the basic idea of how a CEF-based app should look like. For more inspiration, take a look at the cefsimple
and cefclient
apps shipped with the CEF binary distribution.
Disclaimer
This project is incomplete, untested, and most likely unstable, so use it at your own risk. Bug reports and suggestions are welcome though.