mojo/mojo_srcs.gypi - Issue 385983008: Mojo + NaCl prototype.

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/mojo_srcs.gypi

Issue 385983008: Mojo + NaCl prototype. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: Dead files Created 6 years, 4 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:

OLD	NEW
(Empty)
	1 # Copyright 2014 The Chromium Authors. All rights reserved.
	viettrungluu 2014/08/20 19:52:38 I wonder if, instead of adding another .gypi file, I wonder if, instead of adding another .gypi file, you shouldn't reuse mojo_variables.gypi (which I believe was added after you started this change), updating the comment at the top. (At the very least, this file could use a comment indicating what it's for and who uses it....) Nick Bray (chromium) 2014/09/03 23:46:03 Missed this one, looping back and doing it. Show quoted text On 2014/08/20 19:52:38, viettrungluu wrote: > I wonder if, instead of adding another .gypi file, you shouldn't reuse > mojo_variables.gypi (which I believe was added after you started this change), > updating the comment at the top. > > (At the very least, this file could use a comment indicating what it's for and > who uses it....) Missed this one, looping back and doing it.
	2 # Use of this source code is governed by a BSD-style license that can be

	3 # found in the LICENSE file.

	4

	5 {

	6 'variables': {

	7 'mojo_public_system_unittest_sources': [

	8 'public/c/system/tests/core_unittest.cc',

	9 'public/c/system/tests/core_unittest_pure_c.c',

	10 'public/c/system/tests/macros_unittest.cc',

	11 'public/cpp/system/tests/core_unittest.cc',

	12 'public/cpp/system/tests/macros_unittest.cc',

	13 ],

	14 },

	15 }

OLD	NEW