0526aa45e7
* vendor/libchromiumcontent 3f6f01c...588f368 (17): > Merge pull request #8 from aroben/menu-controller > Merge pull request #6 from aroben/shell_dialogs > Fix typo in script/create-dist > Merge pull request #5 from aroben/python > Add libtest_support_chromiumcontent.a > Build and distribute libgtest.a > Stop trying to compile SQLitePersistentCookieStore separately > Update to latest Chromium trunk revision > Merge pull request #4 from aroben/atom > Actually compile the base/prefs code > Export symbols from base/prefs > Compile and export SQLitePersistentCookieStore > Export webkit/plugins headers > Export skia/ext headers > Export ui/surface headers, too > Export Skia symbols from libchromiumcontent > Update to match chrome/trunk |
||
---|---|---|
.. | ||
browser | ||
common | ||
script | ||
tools/mac | ||
vendor | ||
.gitignore | ||
.gitmodules | ||
brightray.gyp | ||
brightray.gypi | ||
LICENSE | ||
LICENSE-CHROMIUM | ||
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
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.