mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions
electron/brightray
History
Adam Roben 9602a9aed9 Fix assertion in InitializeICU on launch 
We have to tell Chromium about our framework bundle earlier in the launch
sequence so it can find icudtl.dat. See
https://codereview.chromium.org/12470006
2014-06-27 11:54:28 -04:00
..
browser Update cookie store code for Chrome 35 2014-06-27 11:54:28 -04:00
common Fix assertion in InitializeICU on launch 2014-06-27 11:54:28 -04:00
script Enable passing --commit to download script. 2014-01-30 22:01:22 +08:00
tools Use abusolute path when linking to external libraries. Fixes #22. 2013-07-02 15:24:24 +08:00
vendor Update libchromiumcontent to Chrome 35 2014-06-27 11:54:15 -04:00
.gitattributes Ensure consistent line endings in all files 2013-05-16 09:15:05 -04:00
.gitignore WIP: builds (but displys nothing) on Linux 2013-11-07 14:02:35 -06:00
.gitmodules Run cpplint as part of our CI build 2013-11-17 17:38:09 -05:00
brightray.gyp Fix include paths for WebIconURL.h 2014-06-27 11:54:27 -04:00
brightray.gypi '-std=gnu++11' is also needed by g++. 2014-01-01 02:29:27 +00:00
LICENSE Initial commit 2013-03-13 15:31:24 -04:00
LICENSE-CHROMIUM Initial commit 2013-03-13 15:31:24 -04:00
README.md Include gyp as a submodule 2013-08-23 07:48:37 -04:00

README.md

Brightray

Brightray is a static library that makes libchromiumcontent easier to use in applications.

Using it in your app

See brightray_example for a sample application written using Brightray.

Development

Prerequisites

  • Python 2.7
  • Linux:
    • Clang 3.0
  • Mac:
    • Xcode
  • Windows:
    • Visual Studio 2010 SP1

One-time setup

You must previously have built and uploaded libchromiumcontent using its script/upload script.

$ script/bootstrap http://base.url.com/used/by/script/upload

Building

$ script/build

Building Brightray on its own isn’t all that interesting, since it’s just a static library. Building it into an application (like brightray_example) is the only way to test it.

License

In general, everything is covered by the LICENSE file. Some files specify at the top that they are covered by the LICENSE-CHROMIUM file instead.