JCEF BUILD

Independent project to produce binary artifacts for the JCef project

Visit the JCEF repo at bitbucket or github

Consider using these builds with Maven or Gradle: jcefmaven

Build Specs:

	amd64, arm64 & arm	amd64 & i386	arm64	amd64 & arm64
Java	OpenJDK 11	Oracle JDK 8	Microsoft JDK 11	Temurin JDK 8
Compiler	GCC 10	VS 2019	VS 2019	Xcode 13
Build	Python 3.7; ninja	Python 3.7; ninja	Python 3.7; ninja	Python 2.7; ninja; SDK10.13
Limitations	-	-	No OSR mode (no Jogamp)	Needs custom structure to run outside of a bundle

You can find the most recent versions of the artifacts on the releases page of this repository.

You have multiple options to build your own project using this repository. They are listed below.

To build another git repo, simply fork this repository. Then go to the "Actions" tab of your forked repository, activate the workflows and manually run the build-all (or build-<platform>) workflow with your repository and commit id/branch specified. This will trigger a build of your desired repository and platforms. To produce a build for MacOS, you will need to specify your code signing information or remove the signing and notarization steps from the action workflows.

Required Actions Secrets for signing and notarization:

+APPLE_API_KEY_BASE64: Your API key to access the Apple Notarization Service (in base64) +APPLE_API_KEY_ISSUER: UUID of issuer (can be found along with your generated key in Apple Dev Console) +APPLE_API_KEY_NAME: The name to be used for your API key on the runner (can be random) +APPLE_API_KEY_ID: The ID of your key (10 digit code) +APPLE_BUILD_CERTIFICATE_BASE64: Base64 encoded pkcs12 certificate file from Apple to use for signing +APPLE_BUILD_CERTIFICATE_NAME: Your certificate name (usually starts with Developer ID Application) +APPLE_P12_PASSWORD: Password of your pkcs12 certificate file +APPLE_KEYCHAIN_PASSWORD: A random password to use for the keychain on the runner +APPLE_TEAM_NAME: Your apple team name, part of the certificate name (10 digit id in brackets)`

You can obtain the api key here (make sure key has developer access) and the certificate here (choose Developer ID Application).

To build locally, put your sources in the jcef directory of this repository, or leave it empty to clone a repository. On Windows and Linux, make sure you installed docker (NOT the Snap version!). On MacOS, make sure you installed the build dependencies specified here and ninja.

Then execute compile-<os>.<sh|bat> <arch> <buildType> [<gitrepo> <gitref>]. Specify an architecture (docker architectures, see script source for options) and build type (Release or Debug). Optionally, you can specify a git repository and ref/branch to pull when no sources are present in the jcef folder.

Please only report bugs here that are related to the build process. Please report bugs in JCEF/CEF to the corresponding repository on Bitbucket.

Feel free to open a pull request on this repository to improve its stability or artifact quality. Make sure to provide a valid GitHub Actions run for your pull requests to be accepted.