mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Robo 9122922133 provide remoteBase to load remote devtools modules
2015-09-30 16:34:44 +05:30
..
browser provide remoteBase to load remote devtools modules 2015-09-30 16:34:44 +05:30
common Fix API changes in DevToolsManagerDelegate. 2015-08-11 09:49:57 +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 Upgrade to Chrome 45 2015-09-02 14:22:50 +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: Fix Release build 2015-08-21 16:19:57 +08:00
brightray.gypi Set MACOSX_DEPLOYMENT_TARGET to 10.8 2015-09-16 19:54:52 +08:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi enabling network emulation in devtools 2015-09-27 21:38:38 +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.