mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Cheng Zhao f1a508f643 win: Link with boringssl.dll
2015-04-06 15:14:57 +08:00
..
browser detecting focus on devtools webcontents 2015-04-01 15:22:53 +05:30
common Enable webui in content layer. 2015-03-29 16:33:51 +08:00
script Download static_library build of libchromiumcontent 2015-04-05 22:28:00 +08:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor win: Link with boringssl.dll 2015-04-06 15:14:57 +08: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 atom org location 2015-03-17 11:24:10 -07:00
brightray.gyp win: Link with boringssl.dll 2015-04-06 15:14:57 +08:00
brightray.gypi win: Fix linking with libyuv 2015-04-06 15:04:07 +08:00
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 atom org location 2015-03-17 11:24:10 -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.