summaryrefslogtreecommitdiffstats
path: root/mojo/mojom_bindings_generator_explicit.gypi
Commit message (Collapse)AuthorAgeFilesLines
* Mojo's WTF dependencies should be set correctly regardless the path depthpeter2016-03-171-2/+2
| | | | | | | | | | | | | Dependency resolution in gyp uses relative paths from the target, so usage of the `for_blink` variable fails for any target that doesn't immediately live in //mojo. This is different from GN, where the dependency is declared absolutely: //mojo/public/cpp/bindings:wtf_support BUG=583738 Review URL: https://codereview.chromium.org/1808253002 Cr-Commit-Position: refs/heads/master@{#381751}
* Mojo C++ bindings: support mapping mojo string to WTF::String.yzshen2016-03-141-0/+19
| | | | | | | | | | The generator now supports a "--for_blink" flag. When it is specified, the generator will map mojo string to WTF::String. BUG=583738 Review URL: https://codereview.chromium.org/1751563002 Cr-Commit-Position: refs/heads/master@{#381091}
* Fix GYP dependency for precompiled Mojo jinja templatesrockot2016-02-111-1/+3
| | | | | | | | | | | | This makes the precompile target a hard_dependency, and ensures that it's always a dependency of any mojom gyp target. BUG=586189 TBR=yzshen@chromium.org Review URL: https://codereview.chromium.org/1693633002 Cr-Commit-Position: refs/heads/master@{#375012}
* [mojo] Delete third_party/mojorockot2016-02-101-0/+139
| | | | | | | | | | | All users are on the new EDK now. This wipes out third_party/mojo, updates all dependencies, and removes the use-new-edk flag. BUG=None Review URL: https://codereview.chromium.org/1676913002 Cr-Commit-Position: refs/heads/master@{#374631}
* Move //mojo/{public, edk} underneath //third_partyblundell2015-01-191-80/+0
| | | | | | | | | | | | | | | | | | | | | | | | This CL move //mojo/public and //mojo/edk to live in the following locations: - //third_party/mojo/src/mojo/public - //third_party/mojo/src/mojo/edk It moves the related gypfiles from //mojo to //third_party/mojo and updates them as necessary to account for the file moves. It also updates clients of the mojo SDK and EDK targets in both GYP and GN. (Note that for GN, the mojo SDK and EDK build systems are maintained in the Mojo repo and designed to be flexible wrt the location of the SDK/EDK in a client repo, so no changes are needed. This CL does not update include paths to the code being moved to limit the number of moving parts, instead relying on the include_dirs that the SDK and EDK targets supply to their direct dependents to ensure that include paths continue to resolve correctly. NOPRESUBMIT=true Review URL: https://codereview.chromium.org/814543006 Cr-Commit-Position: refs/heads/master@{#312129}
* Move mojo gypfiles to toplevel mojorockot2014-12-161-0/+80
These files are owned by chromium now. It would not only be weird to inject them into the rolled mojo directory structure, but doing so would unnecessarily complicate the mojo up-rev procedure. BUG=None TBR=darin@chromium.org Review URL: https://codereview.chromium.org/807773002 Cr-Commit-Position: refs/heads/master@{#308622}