blocks|key|2171645|text|是否将项目从以前的版本升级到Visual+2010？如果是这样，这是一个众所周知的问题.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2171646|Visual+2010+C%2B%2B项目升级指南http://blogs.msdn.com/b/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx|offset|length|2171647|升级期间的|2171648|警告|blockquote|2171649|2171650|以下是您在转换过程中可能遇到的一些常见警告：|2171651|1)链接器输出目录|2171652|升级应用程序时可能会看到的警告之一是MSB8012：$(TargetPath)和Linker的OutputFile属性值不匹配：|2171653|2171654|2171655|MSB8012：$(TargetExt)+('.dll')与项目配置中的OutputFile属性值'C:\foo\Debug\MFCActiveX.ocx‘('.ocx')不匹配。这可能会导致您的项目生成错误。要纠正此情况，请确保$(TargetExt)属性值与%25(Link.OutputFile).|unordered-list-item|2171656|MSB8012：$(TargetPath)+(“C：\foo\Debug\MFCActiveX.dll”)中指定的值不匹配项目配置中的OutputFile属性值“C：\foo\Debug\MFCActiveX.ocx”(“C：\foo\Debug\MFCActiveX.ocx”)。这可能会导致您的项目生成错误。要纠正这一点，请确保$(TargetPath)属性值与%25(Link.OutputFile).|2171657|中指定的值匹配。|2171658|Link.OutputFile是在属性页上的Linker+->通用->输出文件中定义的值。默认情况下，它的值是$(OutDir)$(TargetName)$(TargetExt)，这与$(TargetPath)的值相同。然而，当我们从上一个版本转换一个应用程序时，解析Link.OutputFile并不是一种简单的方法来确定$(TargetName)和$(TargetExt)的确切值，因为不同的客户可能以不同的方式对它们进行了格式化。为了解决这个问题，我们决定在转换期间保留Linker.OutputFile的值。转换后，$(TargetName)将默认为$(ProjectName)。$(TargetExt)默认为应用程序类型的默认扩展:动态库的.dll、静态库的.lib和应用程序的.exe。Link.OutputFile值将被保留。如果MSB8012和$(TargetPath)不一样，则将在转换日志中发出警告TargetPath。在构建应用程序时，您将收到相同的警告。|2171659|$(OutDir),+$(TargetName)+and+$(TargetExt)+are+exposed+on+the+"General"+property+page,+as+"Output+Directory",+"Target+Name",+"Target+Extension",+respectively.+You+can+manually+change+the+values+of+these+properties+so+that+you+no+longer+get+the+warning.|code-block|syntax|javascript|2171660|2171661|如果您的项目生成导入库(Linker+->+Advanced+->+Import+)，则如果Linker输出目录不是默认的输出目录，则可能需要在转换后更改Import的输出文件夹。否则，生成的导入库可能在一个与链接器output.|2171662|Debugging.Command不同的目录中，转换后设置为默认$(TargetPath)。您可能需要进行更改，以便在F5+(调试)或Ctrl+%2B+F5+(开始时不进行调试)上启动正确的可执行文件。|2171663|2171664|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx^0|0|L|2P|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1M|8|@]|9|@$D|1N|E|1O|1|1P]]|A|$]]|$1|F|3|G|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1R|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1T|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1U|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1V|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|1Y|8|@]|9|@]|A|$]]|$1|W|3|X|5|V|7|1Z|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|20|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|21|8|@]|9|@]|A|$]]|$1|12|3|13|5|14|7|22|8|@]|9|@]|A|$15|16]]|$1|17|3|-4|5|6|7|23|8|@]|9|@]|A|$]]|$1|18|3|19|5|V|7|24|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|V|7|25|8|@]|9|@]|A|$]]|$1|1C|3|-4|5|6|7|26|8|@]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|27|8|@]|9|@]|A|$]]]|1E|$1F|$5|1G|1H|1I|A|$1J|1K]]]]

Did you upgrade a project to Visual Studio 2010 from a previous version? If so, this is a well-known issue.

Visual Studio 2010 C++ Project Upgrade Guide
<a href="http://blogs.msdn.com/b/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx" rel="noreferrer">http://blogs.msdn.com/b/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx</a>

<blockquote>
 Warnings during upgrade
 
 Here are some of the common warnings that you may run into during conversion:
 
 1) Linker output directory
 
 One of the warnings you may see when upgrading you applications is MSB8012: $(TargetPath) and Linker’s OutputFile property value does not match:
 
 <ul>
 <li>MSB8012: $(TargetExt) ('.dll') does not match the Linker's OutputFile property value 'C:\foo\Debug\MFCActiveX.ocx' ('.ocx') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetExt) property value matches the value specified in %(Link.OutputFile).</li>
 <li>MSB8012: $(TargetPath) ('C:\foo\Debug\MFCActiveX.dll') does not match the Linker's OutputFile property value 'C:\foo\Debug\MFCActiveX.ocx' ('C:\foo\Debug\MFCActiveX.ocx') in project configuration 'Debug|Win32'. This may cause your project to build incorrectly. To correct this, please make sure that $(TargetPath) property value matches the value specified in %(Link.OutputFile). 
 Link.OutputFile is the value defined at Linker -> General -> Output File on the property page. By default, its value is $(OutDir)$(TargetName)$(TargetExt), which is the same as the value of $(TargetPath). When we convert an application from a previous version, however, there is not an easy way for conversion to parse Link.OutputFile to figure out what exactly the values are for $(TargetName) and $(TargetExt), as different customers may have formatted them in different ways. To work around that, we decided to preserve the value of Linker.OutputFile during conversion. After conversion, $(TargetName) will default to $(ProjectName). $(TargetExt) will default to the default extension for the application type: .dll for Dynamic Library, .lib for Static Library and .exe for Application. Link.OutputFile value will be preserved. Warning MSB8012 will be issued in the conversion log if Link.OutputFile and $(TargetPath) are not the same. You will get the same warnings when building the application. 
 $(OutDir), $(TargetName) and $(TargetExt) are exposed on the "General" property page, as "Output Directory", "Target Name", "Target Extension", respectively. You can manually change the values of these properties so that you no longer get the warning.</li>
 <li>If your project produces Import Library (Linker -> Advanced -> Import Library), you may need to change the Output folder of the Import Library as well after conversion if the Linker output directory is not the default output directory. Otherwise, the generated import lib maybe in a different directory than the linker output.</li>
 <li>Debugging.Command is set to default $(TargetPath) after conversion. You may need to make changes so that the right executable will be launched upon F5 (Debugging) or Ctrl + F5 (Start without debugging).</li>
 </ul>
</blockquote>

blocks|key|52094|text|对于调试DLL，我也遇到了同样的问题，我希望在basename中有一个尾随的"D“。例如，foo.dll+(版本)但是fooD.dll+(调试)。当您在Debug-Configuration的链接器设置中细化输出名称时，就会出现难看的MSB8012警告。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|52095|使用Visual+2010的唯一解决方案似乎是调试配置的Postbuild：|52096|@echo+off
echo+Copying+$(OutDir)$(TargetName)$(TargetExt)+as+$(TargetName)D$(TargetExt)
copy+/Y+$(OutDir)$(TargetName)$(TargetExt)+$(OutDir)$(TargetName)D$(TargetExt)|code-block|syntax|javascript|52097|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The same problem occured to me for debug DLLs, that I wanted to have a trailing "D" in the basename. For example, foo.dll (Release) but fooD.dll (Debug). When you refine the output name in the Linker settings of the Debug-Configuration -- the ugly MSB8012 warning occurs. 

The only solution that works with Visual-Studio 2010 seems to be a Postbuild-Event for the Debug-Configuration:

<pre><code>@echo off
echo Copying $(OutDir)$(TargetName)$(TargetExt) as $(TargetName)D$(TargetExt)
copy /Y $(OutDir)$(TargetName)$(TargetExt) $(OutDir)$(TargetName)D$(TargetExt)
</code></pre>

blocks|key|31182|text|在从旧项目转换到VS+2010之后，我获得了同样的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|31183|为了解决这个问题，我创建了相同类型的空项目(例如.dll、.lib、.exe)。|31184|然后，我将它在Propeties中的默认值复制到输出目录、中间目录和输出文件的项目中。|31185|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I obtained the same error after converting from old project to VS 2010.

To fix this I created empty project of the same type (e.g. .dll, .lib, .exe). 
Then I copied its default values in Project Propeties to my project for Output Directory, Intermediate directory and Output File

blocks|key|2171735|text|也见这里的Stackoverflow+MSB8012。在将VS2008+C%2B%2B项目转换为VS2012时对我起了什么作用:右键单击解决方案资源管理器中的项目，在弹出的:配置属性、链接器、通用中选择属性。选择右边的输出文件，这将给出一个下拉，选择来自父或项目默认值的固有内容。单击apply。这给出了默认的链接器设置：$(OutDir)$(TargetName)$(TargetExt)。重新构建项目和警告不应再出现。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2171736|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/16876429/how-do-i-fix-warning-msb8012-in-a-static-library-project-in-visual-c-2010^0|5|L|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

See also here <a href="https://stackoverflow.com/questions/16876429/how-do-i-fix-warning-msb8012-in-a-static-library-project-in-visual-c-2010">Stackoverflow MSB8012</a>.
What worked for me when converting a VS2008 C++ project to VS2012: right click the project in solution explorer, select properties, in the pop-up: configuration properties, linker, general. Select Output file on the right, this gives a drop-down, select inherent from parent or project defaults. Click apply. This gives the default linker setting: $(OutDir)$(TargetName)$(TargetExt). Re-build the project and the warning should no longer appear.

blocks|key|52199|text|我有这样的场景:我的可执行文件名与项目名称不同，我希望它将可执行文件/dll构建到与项目所在位置不同的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|52200|1)将默认项目名称更改为不同。一般->TargetName|52201|<我的可执行name>|52202|2)输出到我希望可执行文件生成的不同位置。General->OutputDirectory+<我的新位置在这里>|52203|3)更新链接器设置。链接器->一般新值：$(OutDir)$(TargetName)$(TargetExt)|52204|这将从1和2接受新的设置。|52205|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I had the scenario where my executable name was different than the project name AND I wanted it to build the executable/dll to a different location than where the project was located.

1)Change the default project name to be different.
 General->TargetName 
 &lt; my executable name>

2) Output to a different location where I want the executable to build.
 General->OutputDirectory
 &lt; my new location goes here >

3) Update the Linker settings.
 Linker->General
 new value: $(OutDir)$(TargetName)$(TargetExt) 
This takes on the new settings from 1 and 2.

blocks|key|31245|text|通过手动编辑vcxproj文件，我成功地修复了一个类似的问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|31246|OutDir和TargetName设置位于项目文件的底部。|31247|+++...
++++++<PropertyGroup+Condition="'$(Configuration)%7C$(Platform)'=='Release%7CWin32'">
++++++++<OutDir>$(OUTPUT_DIRECTORY)\</OutDir>
++++++++<IntDir>$(ProjectDir)\$(Configuration)\$(ProjectName)\</IntDir>
++++++++<TargetName>$(ProjectName)</TargetName>
++++++</PropertyGroup>
+++</Project>|code-block|syntax|javascript|31248|将块移到ClCompile块之上解决了这个问题。|31249|entityMap^0|6|7|0|0|6|7|A|0|0|4|9|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|P|$]]

I managed to fix a similar issue by editing the <code>vcxproj</code> file manually.

The <code>OutDir</code> and <code>TargetName</code> settings were at the bottom of the project file.

<pre><code> ...
 &lt;PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"&gt;
 &lt;OutDir&gt;$(OUTPUT_DIRECTORY)\&lt;/OutDir&gt;
 &lt;IntDir&gt;$(ProjectDir)\$(Configuration)\$(ProjectName)\&lt;/IntDir&gt;
 &lt;TargetName&gt;$(ProjectName)&lt;/TargetName&gt;
 &lt;/PropertyGroup&gt;
 &lt;/Project&gt;
</code></pre>

Moving the block above the <code>ClCompile</code> block solved the issue.

blocks|key|2171792|text|我通过把这个项目和一个非常相似的项目进行比较来解决这个问题。项目属性中的所有设置都匹配，但我在故障项目的vcxproj文件中发现了以下额外行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2171793|<Lib>
+++<OutputFile>.\MCtlDrvX.lib</OutputFile>
</Lib>|code-block|syntax|javascript|2171794|我删除了它们，消息消失了，输出转到项目设置中指定的目录中。|2171795|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I solved this by comparing the project to a very similar project that was working properly. All of the settings in the project properties matched but I found the following extra lines in the vcxproj file of the malfunctioning project:

<pre><code>&lt;Lib&gt;
 &lt;OutputFile&gt;.\MCtlDrvX.lib&lt;/OutputFile&gt;
&lt;/Lib&gt;
</code></pre>

I deleted them and the message went away and the output went to the directory specified in the project settings.

blocks|key|31310|text|Goto+>+Properties+->+Configuration+Properties->+Linker->General节|type|unstyled|depth|inlineStyleRanges|entityRanges|data|31311|将“输出文件”指定为$(OutDir)$(TargetName)$(TargetExt)|31312|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Goto Project->Properties->Configuration Properties -> Linker->General section

Specify 'Output File' as $(OutDir)$(TargetName)$(TargetExt)

I am getting the following error when building my code.

<blockquote>
 C:\Program Files
 (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5):
 warning MSB8012:
 TargetPath(E:\Study\FWIF\demola\ext-libs\libcommoncpp2-1.6.0\w32\Debug\ccgnu2.dll)
 does not match the Linker's OutputFile property value
 g\CapeCommon14.dll). This may cause your project to build incorrectly.
 To correct this, please make sure that $(OutDir), $(TargetName) and
 $(TargetExt) property values match the value specified in
 %(Link.OutputFile).
</blockquote>

I hope that some one will know what to do.

warning MSB8012 : make sure that $(OutDir), $(TargetName) and $(TargetExt) property values match the value specified in %(Link.OutputFile)

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

在构建代码时，我会得到以下错误。Linker C:\Program (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets(990,5)：警告MSB8012: TargetPath(E:\Study\FWIF\demola\ext-libs\libcomm...

问警告MSB8012 :确保$(OutDir)、$(TargetName)和$(TargetExt)属性值与%(Link.OutputFile)中指定的值匹配
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问警告MSB8012 :确保$(OutDir)、$(TargetName)和$(TargetExt)属性值与%(Link.OutputFile)中指定的值匹配EN