mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Cheng Zhao 8488425e06 Link with fontsub.lib
2017-01-27 17:11:33 +09:00
..
browser libgtk2ui => libgtkui 2017-01-26 20:02:01 +09:00
common Fix API changes of Chrome 53 2016-09-06 17:22:52 +09:00
script Build through Electron in cibuild and add Travis config 2017-01-12 11:37:52 -08:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor libgtk2ui => libgtkui 2017-01-26 20:02:01 +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
.travis.yml Build through Electron in cibuild and add Travis config 2017-01-12 11:37:52 -08:00
appveyor.yml Add initial AppVeyor config 2017-01-12 11:38:12 -08:00
brightray.gyp Link with fontsub.lib 2017-01-27 17:11:33 +09:00
brightray.gypi Add /LARGEADDRESSAWARE to linker options (Windows) 2016-10-05 18:32:24 +02:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi persist media device id salt across sessions 2016-12-03 16:47:31 +05:30
LICENSE Time goes on 2014-07-11 00:39:21 -07:00
LICENSE-CHROMIUM
README.md Link to electron instead of brightray_example 2016-10-03 15:46:09 -07:00

README.md

Brightray

Brightray is a static library that makes libchromiumcontent easier to use in applications.

Using it in your app

See electron for example of an 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 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.