chrome/tools/build/linux/FILES.cfg - Issue 2799006: Update installer for internal plugin.

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: chrome/tools/build/linux/FILES.cfg

Issue 2799006: Update installer for internal plugin. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/

Patch Set: '' Created 10 years, 6 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
1 # -- python --	1 # -- python --

2 # ex: set syntax=python:	2 # ex: set syntax=python:

3	3

4 # Copyright (c) 2010 The Chromium Authors. All rights reserved.	4 # Copyright (c) 2010 The Chromium Authors. All rights reserved.

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

6 # found in the LICENSE file.	6 # found in the LICENSE file.

7	7

8 # This is a buildbot configuration file containing a tagged list of files	8 # This is a buildbot configuration file containing a tagged list of files

9 # processed by the stage/archive scripts. The known tags are:	9 # processed by the stage/archive scripts. The known tags are:

10 #	10 #

(...skipping 73 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
84 {	84 {

85 'filename': 'libgcflashplayer.so',	85 'filename': 'libgcflashplayer.so',

86 'arch': ['32bit'],	86 'arch': ['32bit'],

87 'buildtype': ['official'],	87 'buildtype': ['official'],

88 },	88 },

89 {	89 {

90 'filename': 'plugin.vch',	90 'filename': 'plugin.vch',

91 'arch': ['32bit'],	91 'arch': ['32bit'],

92 'buildtype': ['official'],	92 'buildtype': ['official'],

93 },	93 },

	94 # PDF Plugin files:
	viettrungluu 2010/06/15 01:45:43 Now that I think of it, I'm also worried about the Now that I think of it, I'm also worried about the official versus non-official build thing (but then I don't know why the Flash files are in win/FILES). jam 2010/06/15 01:52:07 think of this binary as more like any chrome binar Show quoted text On 2010/06/15 01:45:43, viettrungluu wrote: > Now that I think of it, I'm also worried about the official versus non-official > build thing (but then I don't know why the Flash files are in win/FILES). think of this binary as more like any chrome binary that we can distribute however we want, except that the code isn't open.
	95 {

	96 'filename': 'libpdf.so',

	97 'arch': ['32bit', '64bit'],

	98 'buildtype': ['dev', 'official'],

	99 },

94 ]	100 ]

OLD	NEW

« chrome/installer/mini_installer/chrome_frame.release ('K') | « chrome/tools/build/linux/FILES ('k') | chrome/tools/build/win/FILES » ('j') | chrome/tools/build/win/FILES.cfg » ('J')