History

Adam Roben 2582e8561c Update to Chromium r202921 * vendor/libchromiumcontent 0d02a8d...2f53a96 (1): > Merge pull request #14 from brightray/latest-chromium		2013-05-30 15:07:32 -04:00
..
browser	Update to Chromium r202921	2013-05-30 15:07:32 -04:00
common	Update to Chromium r202921	2013-05-30 15:07:32 -04:00
script	Use MSBuild to build on Windows	2013-05-16 09:15:54 -04:00
tools/mac	Initial commit	2013-03-13 15:31:24 -04:00
vendor	Update to Chromium r202921	2013-05-30 15:07:32 -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	Update for libchromiumcontent repo transfer	2013-05-14 09:26:40 -04:00
brightray.gyp	Automatically exclude platform-specific files for all targets	2013-05-28 14:27:57 -04:00
brightray.gypi	Update to Chromium r202921	2013-05-30 15:07:32 -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	Update links after move to brightray org	2013-05-21 14:57:52 -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
gyp
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