summaryrefslogtreecommitdiffstats
path: root/remoting/remoting.gyp
diff options
context:
space:
mode:
authoriannucci@chromium.org <iannucci@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-11-17 00:28:42 +0000
committeriannucci@chromium.org <iannucci@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-11-17 00:28:42 +0000
commit45a77070ad256f2b6c0ed31cacdc5592582ef598 (patch)
treed5e6caa5aba3fe36cb5a85dff707877933b76a7b /remoting/remoting.gyp
parent3fb32e142a83a6d65e5c309ef8478c315ce2be0a (diff)
downloadchromium_src-45a77070ad256f2b6c0ed31cacdc5592582ef598.zip
chromium_src-45a77070ad256f2b6c0ed31cacdc5592582ef598.tar.gz
chromium_src-45a77070ad256f2b6c0ed31cacdc5592582ef598.tar.bz2
Make all pdb file names follow the same naming convention.
The new naming scheme simply appends .pdb to the target (e.g. foo.dll.pdb and foo.exe.pdb). This is beneficial for a couple reasons: * no more chrome_dll.pdb and chrome_exe.pdb silliness * also avoids this issue if we end up with similarly named targets in the future (target.dll and target.exe) * ninja already does this, and, by extension, either ninja needs to be broken to use the old scheme, or the we fix the broken in the existing system. One less difference between msvs and ninja. Fixes for chrome-internal stuff: https://chromereviews.googleplex.com/5681015 BUG= Review URL: https://codereview.chromium.org/11384003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168341 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/remoting.gyp')
-rw-r--r--remoting/remoting.gyp1
1 files changed, 0 insertions, 1 deletions
diff --git a/remoting/remoting.gyp b/remoting/remoting.gyp
index 002db29..7dabdd1 100644
--- a/remoting/remoting.gyp
+++ b/remoting/remoting.gyp
@@ -1845,7 +1845,6 @@
],
'ImportLibrary': '$(OutDir)\\lib\\remoting_host_exe.lib',
'OutputFile': '$(OutDir)\\remoting_host.exe',
- 'ProgramDatabaseFile': '$(OutDir)\\remoting_host.pdb',
# 2 == /SUBSYSTEM:WINDOWS
'SubSystem': '2',
},