mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Cheng Zhao 11685faffa Hijack the Page.reload command
2016-04-12 16:35:35 +09:00
..
browser Hijack the Page.reload command 2016-04-12 16:35:35 +09:00
common Pass() is deprecated for std::move 2016-03-08 20:59:29 +09:00
script Fix build error 2015-11-10 23:26:42 +09:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor Update to lastest master of libchromiumcontent 2016-03-11 10:41:22 +09:00
.gitattributes Ensure consistent line endings in all files 2013-05-16 09:15:05 -04:00
.gitignore Ignore a couple more files on Windows 2014-06-27 13:45:04 -04:00
.gitmodules Update urls for new GitHub org 2016-04-04 12:55:40 -07:00
brightray.gyp Dealy loading powrprof.dll 2016-03-13 10:10:56 +09:00
brightray.gypi allow setting pkg-config variable 2016-03-09 19:43:55 +05:30
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi update devtools network interceptor to throttle uploads 2016-03-14 04:01:30 +05:30
LICENSE Time goes on 2014-07-11 00:39:21 -07:00
LICENSE-CHROMIUM Initial commit 2013-03-13 15:31:24 -04:00
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.