How to get rid of warnings from MSBUILD ?

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello,

Our company switched over to a 'No warnings at warning level 4' policy. All of our products was cleaned up, but one project is still on the focus...

I'm using Visual Studio 2013 and the compiler produces constantly these warnings:

1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(1361,5): warning MSB8012: TargetPath(E:\Ankhor\trunk\vendor\Xtreme ToolkitPro v16.3.1\Workspace\ToolkitPro\.\Dynamic_Unicode_Debug/vc120\Codejock.ToolkitPro.Static.lib) does not match the Library's OutputFile property value (E:\Ankhor\trunk\vendor\Xtreme ToolkitPro v16.3.1\lib\vc120\ToolkitPro1631vc120DSUD.lib). 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 %(Lib.OutputFile).
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(1363,5): warning MSB8012: TargetName(Codejock.ToolkitPro.Static) does not match the Library's OutputFile property value (ToolkitPro1631vc120DSUD). 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 %(Lib.OutputFile).

In theory I know how to fix them ( I did this for all our projects ), but wouldn't it be possible for CodeJock to fix them also for the Toolkit ?

Or please provide a method how to suppress them...

Best regards,
Alex

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Alex G. Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 22 December 2004 Location: Germany Status: Offline Points: 74	Post Options Post Reply Quote Alex G. Report Post Thanks(0) Quote Reply Topic: How to get rid of warnings from MSBUILD ? Posted: 05 June 2014 at 2:42am
	Hello, Our company switched over to a 'No warnings at warning level 4' policy. All of our products was cleaned up, but one project is still on the focus... I'm using Visual Studio 2013 and the compiler produces constantly these warnings: 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(1361,5): warning MSB8012: TargetPath(E:\Ankhor\trunk\vendor\Xtreme ToolkitPro v16.3.1\Workspace\ToolkitPro\.\Dynamic_Unicode_Debug/vc120\Codejock.ToolkitPro.Static.lib) does not match the Library's OutputFile property value (E:\Ankhor\trunk\vendor\Xtreme ToolkitPro v16.3.1\lib\vc120\ToolkitPro1631vc120DSUD.lib). 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 %(Lib.OutputFile). 1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.CppBuild.targets(1363,5): warning MSB8012: TargetName(Codejock.ToolkitPro.Static) does not match the Library's OutputFile property value (ToolkitPro1631vc120DSUD). 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 %(Lib.OutputFile). In theory I know how to fix them ( I did this for all our projects ), but wouldn't it be possible for CodeJock to fix them also for the Toolkit ? Or please provide a method how to suppress them... Best regards, Alex

mcmastl Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 14 April 2015 Status: Offline Points: 79	Post Options Post Reply Quote mcmastl Report Post Thanks(0) Quote Reply Posted: 15 April 2015 at 2:36pm
	Hi Alex, we have informed our development team of the issue and will be looking into it. Thank you for bringing this to our attention. If the issue has been resolved please let us know. Thank you.
	Luke McMasters, Support Team CODEJOCK SOFTWARE SOLUTIONS