mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Adam Roben 90e1370d7f Update libchromiumcontent for Windows support 
* vendor/libchromiumcontent e70a88f...4aae27b (2):
  > Merge pull request #11 from brightray/windows-build
  > Merge pull request #10 from brightray/windows-scripts
2013-05-16 08:54:01 -04:00
..
browser frontend_host_ should be destructed after devtools_web_contents_. 2013-05-01 22:00:20 +08:00
common Fix crashes when dragging links 2013-04-26 22:49:58 -04:00
script Add script/cibuild 2013-05-14 12:20:50 -04:00
tools/mac Initial commit 2013-03-13 15:31:24 -04:00
vendor Update libchromiumcontent for Windows support 2013-05-16 08:54:01 -04:00
.gitignore Initial commit 2013-03-13 15:31:24 -04:00
.gitmodules Update for libchromiumcontent repo transfer 2013-05-14 09:26:40 -04:00
brightray.gyp Include the application's version number in the user agent string 2013-04-08 12:41:30 -04:00
brightray.gypi Turn off C++ exceptions 2013-04-26 14:13:45 -04:00
LICENSE Initial commit 2013-03-13 15:31:24 -04:00
LICENSE-CHROMIUM Initial commit 2013-03-13 15:31:24 -04:00
README.md Initial commit 2013-03-13 15:31:24 -04: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

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.