electron/brightray
Adam Roben d32a2fbc97 Update libchromiumcontent to get ICU headers
* vendor/libchromiumcontent ee4cea0...33472d4 (5):
  > Export ICU headers
  > When `gclient sync` fails, revert all local changes and try again
  > Merge pull request #23 from brightray/chromiumviews_pdb
  > Merge pull request #22 from brightray/cygwin2
  > Update to Chrome 28.0.1500.71
2013-07-25 12:22:58 -04:00
..
browser Avoid a crash when starting a download by disallowing downloads 2013-07-24 07:56:55 -04:00
common Rename the Helper process to Renderer/Plug-In Host/Utility as appropriate 2013-07-17 11:04:45 -04:00
script Use MSBuild to build on Windows 2013-05-16 09:15:54 -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 ICU headers 2013-07-25 12:22:58 -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 Avoid a crash when starting a download by disallowing downloads 2013-07-24 07:56:55 -04:00
brightray.gypi Always build 32-bit in Xcode 2013-07-08 12:17:48 -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

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 isnt all that interesting, since its 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.