mojo/bindings/java/BUILD.gn - Issue 388333003: Add GN build targets for the rest of mojo/public

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: mojo/bindings/java/BUILD.gn

Issue 388333003: Add GN build targets for the rest of mojo/public (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Add //mojo/bindings/java to mojo group on android builds Created 6 years, 5 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 # Copyright 2014 The Chromium Authors. All rights reserved.

	2 # Use of this source code is governed by a BSD-style license that can be

	3 # found in the LICENSE file.

	4

	5 import("//build/config/android/rules.gni")

	6

	7 android_library("mojo_public_java") {
	yzshen1 2014/07/15 20:59:59 The style guide suggests using short (possibly non The style guide suggests using short (possibly non-unique) names that make writing dependencies clearer, "mojo_" is probably not needed. Besides, why we use "public_" in the name? Chris Masone 2014/07/15 21:11:06 Copy-paste error! Didn't know that about the style Show quoted text On 2014/07/15 20:59:59, yzshen1 wrote: > The style guide suggests using short (possibly non-unique) names that make > writing dependencies clearer, "mojo_" is probably not needed. > > Besides, why we use "public_" in the name? Copy-paste error! Didn't know that about the style guide, I'll follow that convention.
	8 java_files = [

	9 "src/org/chromium/mojo/bindings/BindingsHelper.java",

	10 "src/org/chromium/mojo/bindings/Callbacks.java",

	11 "src/org/chromium/mojo/bindings/Connector.java",

	12 "src/org/chromium/mojo/bindings/Decoder.java",

	13 "src/org/chromium/mojo/bindings/DeserializationException.java",

	14 "src/org/chromium/mojo/bindings/Encoder.java",

	15 "src/org/chromium/mojo/bindings/ExecutorFactory.java",

	16 "src/org/chromium/mojo/bindings/HandleOwner.java",

	17 "src/org/chromium/mojo/bindings/Interface.java",

	18 "src/org/chromium/mojo/bindings/InterfaceRequest.java",

	19 "src/org/chromium/mojo/bindings/InterfaceWithClient.java",

	20 "src/org/chromium/mojo/bindings/Message.java",

	21 "src/org/chromium/mojo/bindings/MessageReceiver.java",

	22 "src/org/chromium/mojo/bindings/Struct.java",

	23 ]

	24 }

OLD	NEW

« mojo/BUILD.gn ('K') | « mojo/BUILD.gn ('k') | mojo/mojo_public.gypi » ('j') | mojo/public/BUILD.gn » ('J')