History

Cheng Zhao c72c89bd75 No more basictypes.h		2016-03-08 10:14:16 +09:00
..
browser	No more basictypes.h	2016-03-08 10:14:16 +09:00
common	Initialize resource bundle on browser process separately	2016-01-08 12:04:23 +08:00
script	Fix build error	2015-11-10 23:26:42 +09:00
tools/mac	Link with component build shared libraries	2015-04-02 14:05:43 +08:00
vendor	Update to Chrome 49	2016-03-08 10:04:06 +09: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 ffmpeg	2016-02-17 22:20:40 +08:00
brightray.gypi	Initialize resource bundle on browser process separately	2016-01-08 12:04:23 +08:00
filename_rules.gypi	Move filename rules to another file	2015-04-09 10:03:01 +08:00
filenames.gypi	Remove DefaultWebContentsDelegate	2016-02-01 21:08:52 +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.

README.md Unescape Escape