mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Cheng Zhao 64c4a34507 Make devtools_web_contents_ is destroyed before everything 
The WebContentsDestroyed still access the other members, so if they are
destroyed before the devtools_web_contents_ in the destructor, we will
crash there.
2015-06-09 10:44:48 +08:00
..
browser Make devtools_web_contents_ is destroyed before everything 2015-06-09 10:44:48 +08:00
common Update cpplint 2015-06-05 12:07:27 +08:00
script Require target_arch parameter 2015-04-11 18:29:51 +08:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor Update cpplint 2015-06-05 12:07:27 +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 Link with gmodule-2.0, fix atom/electron#1809 2015-06-04 14:41:16 +08:00
brightray.gypi Suppress compiler warning 2015-05-23 11:10:40 +08:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi adding support for kLogNetLog switch 2015-06-05 20:25:08 +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 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.