History

Cheng Zhao aba65c23f6 Give user a chance to override child process and framework path.		2014-07-09 17:07:00 +08:00
..
browser	Allow access FileSystem api in devtools.	2014-07-09 15:38:53 +08:00
common	Give user a chance to override child process and framework path.	2014-07-09 17:07:00 +08:00
script	Fix cpplint warning for obj-c header.	2014-07-09 10:38:00 +08:00
tools	Use abusolute path when linking to external libraries. Fixes #22 .	2013-07-02 15:24:24 +08:00
vendor	Update libchromiumcontent for better Chrome 35 support	2014-07-07 12:27:38 -04: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	Run cpplint as part of our CI build	2013-11-17 17:38:09 -05:00
brightray.gyp	Remove Windows's devtools implementation.	2014-07-09 10:37:54 +08:00
brightray.gypi	Ignore *_views files on mac.	2014-07-09 10:26:01 +08: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	Include gyp as a submodule	2013-08-23 07:48:37 -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

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