bcarrella/cef
1
0
Fork 0
mirror of https://bitbucket.org/chromiumembedded/cef synced 2024-12-26 09:34:14 +01:00
Code Issues Packages Projects Releases Wiki Activity
b070564ec5
cef/tools/distrib
History
Marshall Greenblatt 980cc4b9fe bazel: win: Explicitly link libcef.lib in cc_binary (see #3757) 
Using cc_import + interface_library/shared_library to link libcef.lib causes
libcef.dll to be copied as a transitive dependency, leading to issues with
complex Bazel configs. Instead, we explicitly link libcef.lib in the binary
target (cc_binary + linkopts/additional_linker_inputs) and explicitly copy
libcef.dll to the target directory.
2024-11-05 11:47:54 -05:00
..
bazel bazel: win: Explicitly link libcef.lib in cc_binary (see #3757) 2024-11-05 11:47:54 -05:00
gtest Check in fused GTest files 2021-08-24 17:43:02 -04:00
linux bazel: Add initial config for binary distribution (see #3757) 2024-07-28 18:19:47 +00:00
mac bazel: Add initial config for binary distribution (see #3757) 2024-07-28 18:19:47 +00:00
tools distrib: Add new tools distribution for mksnapshot (see #3734) 2024-07-16 12:43:12 -04:00
win bazel: Add initial config for binary distribution (see #3757) 2024-07-28 18:19:47 +00:00
README-TRANSFER.txt
README.client.txt
README.footer.txt
README.header.txt Fix README typo 2017-12-18 14:18:03 -05:00
README.tools.txt distrib: Add new tools distribution for mksnapshot (see #3734) 2024-07-16 12:43:12 -04:00
transfer_standard.cfg Don't include ceftests/resources in minimal distrib (fixes issue #3408) 2022-10-10 14:11:22 -04:00
transfer.cfg win: Fix MSVC compile error with cef_color_ids.h (see #3671) 2024-04-11 11:29:51 -04:00

README.tools.txt 

CONTENTS
--------

Debug       Contains the Debug build of tools.

Release     Contains the Release build of tools.


IMPORTANT NOTE
--------------

CEF/Chromium builds are created using the following host architectures:

- Linux:   x86-64 (Intel/AMD)
- Windows: x86-64 (Intel/AMD)
- MacOS:   ARM64 (Apple Silicon)

Binaries in this tools package must be run on the supported host OS/architecture
even in cases where the output targets a different architecture.

For example, files targeting a MacOS 64-bit (Intel) application must be created
on a MacOS ARM64 (Apple Silicon) host system using the MacOS 64-bit (Intel)
tools distribution.


USAGE
-----

Start with the required host system and the tools distribution that matches your
application's target OS/architecture and CEF version.

Custom V8 Snapshots

Custom startup snapshots [https://v8.dev/blog/custom-startup-snapshots] can be
used to speed up V8/JavaScript load time in the renderer process. With CEF this
works as follows:

1. Generate a single JavaScript file that contains custom startup data. For
   example, using https://github.com/atom/electron-link.

2. Execute the `run_mksnapshot` script to create a `v8_context_snapshot.bin`
   file containing the custom data in addition to the default V8 data.

   Example:
   % run_mksnapshot Release /path/to/snapshot.js

   Note that bin file names include an architecture component on MacOS
   (e.g. `v8_context_snapshot.[arm64|x86_64].bin`)

3. Replace the existing `v8_context_snapshot.bin` file in the installation
   folder or app bundle.

4. Run the application and verify in DevTools that the custom startup data
   exists. For example, electron-link adds a global `snapshotResult` object.

Please visit the CEF Website for additional usage information.

https://bitbucket.org/chromiumembedded/cef/