mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Cheng Zhao d435df77f8 Revert "initialize crypto delegate in CookieStoreConfig" 
This reverts commit ad1d1dce72c6fcb6c15a18dac04ff382d9bf4db0.
2016-09-19 16:30:16 +09:00
..
browser Revert "initialize crypto delegate in CookieStoreConfig" 2016-09-19 16:30:16 +09:00
common Fix API changes of Chrome 53 2016-09-06 17:22:52 +09:00
script Do not check existence of paths 2016-05-02 16:17:20 +09:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor Update to Chrome 53.0.2785.113 2016-09-15 14:27:07 +09:00
.gitattributes
.gitignore Ignore a couple more files on Windows 2014-06-27 13:45:04 -04:00
.gitmodules Update gyp with support for CLANG_ENABLE_OBJC_WEAK 2016-05-13 13:49:15 +09:00
brightray.gyp Revert "initialize crypto delegate in CookieStoreConfig" 2016-09-19 16:30:16 +09:00
brightray.gypi Target OS X 10.9 2016-09-08 15:24:27 +09:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi allow additional schemes that should support cookies 2016-08-03 15:52:09 +05:30
LICENSE Time goes on 2014-07-11 00:39:21 -07:00
LICENSE-CHROMIUM
README.md Update urls for new GitHub org 2016-04-04 12:55:40 -07: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.