mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1
electron/brightray
History
Cheng Zhao 5e807cffc8 Use abusolute path when linking to external libraries. Fixes #22. 
The ninja generator of gyp behaves strangely on the 'libraries' field of link
settings, for example, specifying path to an external library works well on
both xcodebuild and msvc generators, but the ninja generator would link to
the wrong path (it can neither translate relative path correctly, nor convert
the command line parameter to the '-lxxx' form).

The only way to make all generators work on all platforms is to use abusolute
paths for external libraries.
2013-07-02 15:24:24 +08:00
..
browser Give BrowserContext subclasses access to GetPath() 2013-06-06 18:50:37 -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 Use abusolute path when linking to external libraries. Fixes #22. 2013-07-02 15:24:24 +08:00
vendor Update to latest libchromiumcontent 2013-06-06 18:50:55 -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 Use abusolute path when linking to external libraries. Fixes #22. 2013-07-02 15:24:24 +08:00
brightray.gypi Implement undocked dev tools on Windows 2013-06-04 14:33:29 -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.