mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Adam Roben d54f4e2bdd Update libchromiumcontent to get icudt.dll 
* vendor/libchromiumcontent 31efc77...e436974 (2):
  > Export icudt.dll for Windows clients
  > Export libGLESv2.dll on Windows
2013-05-22 14:04:28 -04:00
..
browser ifdef out a bunch of Mac-specific code 2013-05-22 13:55:56 -04:00
common Set up the resource bundle on Windows 2013-05-22 14:00:43 -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 libchromiumcontent to get icudt.dll 2013-05-22 14:04:28 -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 Exclude platform-specific files from other platforms 2013-05-22 14:00:43 -04:00
brightray.gypi Link against the DLL version of the CRT 2013-05-22 14:00:31 -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.