History

Patrick Reynolds 90e619a6d9 fix typo		2013-11-07 17:25:51 -06:00
..
browser	fix typo	2013-11-07 17:25:51 -06:00
common	Rename the Helper process to Renderer/Plug-In Host/Utility as appropriate	2013-07-17 11:04:45 -04:00
script	Build using make on Linux	2013-08-06 17:25:07 -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 get better Linux support	2013-08-06 16:43:21 -04:00
.gitattributes	Ensure consistent line endings in all files	2013-05-16 09:15:05 -04:00
.gitignore	WIP: builds (but displys nothing) on Linux	2013-11-07 14:02:35 -06:00
.gitmodules	Update for libchromiumcontent repo transfer	2013-05-14 09:26:40 -04:00
brightray.gyp	WIP: builds (but displys nothing) on Linux	2013-11-07 14:02:35 -06: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	Mention that Clang 3.0 is needed on Linux	2013-08-14 08:17: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
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