History

Adam Roben c0e744db78 Update libchromiumcontent to use Xcode's clang * vendor/libchromiumcontent 759a8d0...21d99bd (1): > Merge pull request #28 from brightray/xcode-clang		2013-10-09 12:58:36 -04:00
..
browser	Make MediaStreamDevicesController::Accept/Deny public again	2013-10-07 17:04:40 -04:00
common	Update #includes for moves of string-related headers	2013-10-07 16:31:57 -04:00
script	Include gyp as a submodule	2013-08-23 07:48:37 -04:00
tools	Use abusolute path when linking to external libraries. Fixes #22 .	2013-07-02 15:24:24 +08:00
vendor	Update libchromiumcontent to use Xcode's clang	2013-10-09 12:58:36 -04:00
.gitattributes	Ensure consistent line endings in all files	2013-05-16 09:15:05 -04:00
.gitignore	Beef up .gitignore	2013-05-22 13:54:07 -04:00
.gitmodules	Include gyp as a submodule	2013-08-23 07:48:37 -04:00
brightray.gyp	Update ICU header include path	2013-10-07 17:02:35 -04:00
brightray.gypi	Compile as C++11 on Linux	2013-08-14 08:14:54 -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	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