[Mono-dev] Recent xbuild fixes causing issues with finding mcs

[Michael Franz]

Hi,

I see there have been a few changes to xbuild since February 10th, 2014.
 February 10th is the last time I was able to build my local C# project
using mono head.  This is a simple project that I have just started and am
planing to build on both mono and .NET.  The issue seems to be that xbuild
has changed how it finds mcs.  /opt/local/JenkinsBuilds/bin/mcs ->
/opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe - see below.

My locally build mono install is in /opt/local/JenkinsBuilds and my builds
are all run via Jenkins.

The build process is:
- use premake5 to generate Visual Studio 2012 project files (note I am
using .net 4.5 specific features)
- use xbuild to build
- use mono version of nunit to test

The working build out put was like this:

+ /opt/local/JenkinsBuilds/bin/xbuild QTS.sln
XBuild Engine Version 12.0
Mono, Version 3.2.7.0
Copyright (C) 2005-2013 Various Mono authors

Build started 2/10/2014 9:56:00 PM.
__________________________________________________
Project "/var/lib/jenkins/jobs/CI/workspace/QTS.sln" (default target(s)):
	Target ValidateSolutionConfiguration:
		Building solution configuration "Debug|Any CPU".
	Target Build:
		Project "/var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj" (default
target(s)):
			Target PrepareForBuild:
				Configuration: Debug Platform: AnyCPU
			Target GenerateSatelliteAssemblies:
			No input files were specified for target
GenerateSatelliteAssemblies, skipping.
			Target GenerateTargetFrameworkMonikerAttribute:
			Skipping target "GenerateTargetFrameworkMonikerAttribute" because
its outputs are up-to-date.
			Target CoreCompile:
				Tool */opt/local/JenkinsBuilds/bin/mcs* execution started with
arguments: /noconfig /debug:full /debug+ /optimize-
/out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs
Utilities/Measurements/PerformanceStatistics.cs /target:library
/define:"DEBUG;TRACE" /platform:AnyCPU
/reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll
/reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll
/warn:4


The broken build is now producing:

+ /opt/local/JenkinsBuilds/bin/xbuild QTS.sln
XBuild Engine Version 12.0
Mono, Version 3.2.7.0
Copyright (C) 2005-2013 Various Mono authors

Build started 2/15/2014 8:50:52 AM.
__________________________________________________
Project "/var/lib/jenkins/jobs/CI/workspace/QTS.sln" (default target(s)):
	Target ValidateSolutionConfiguration:
		Building solution configuration "Debug|Any CPU".
	Target Build:
		Project "/var/lib/jenkins/jobs/CI/workspace/QTS/QTS.csproj" (default
target(s)):
			Target PrepareForBuild:
				Configuration: Debug Platform: AnyCPU
				Created directory "bin/Debug/"
				Created directory "obj/Debug/"
			Target CopyFilesMarkedCopyLocal:
				Copying file from
'/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll' to
'/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll'
				Copying file from
'/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll.mdb' to
'/var/lib/jenkins/jobs/CI/workspace/QTS/bin/Debug/mscorlib.dll.mdb'
			Target GenerateSatelliteAssemblies:
			No input files were specified for target
GenerateSatelliteAssemblies, skipping.
			Target CoreCompile:
				Tool /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe execution
started with arguments: /noconfig /debug:full /debug+ /optimize-
/out:obj/Debug/QTS.dll Properties/AssemblyInfo.cs Utilities/Math.cs
Utilities/Measurements/PerformanceStatistics.cs
obj/Debug/.NETFramework,Version=v4.5.AssemblyAttribute.cs
/target:library /define:"DEBUG;TRACE" /nostdlib /platform:AnyCPU
/reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.dll
/reference:/opt/local/JenkinsBuilds/lib/mono/4.5/System.Core.dll
/reference:/opt/local/JenkinsBuilds/lib/mono/4.5/mscorlib.dll /warn:4
/opt/local/JenkinsBuilds/lib/mono/4.5/Microsoft.CSharp.targets: error
: Error executing tool
'/opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe':



I checked the commit logs, and it looks like there are commits that would
affect this behavior.  Now, it might be that I was doing something wrong
from the start and now I need to fix the process, but it seems like a
simple process.
e753ca2 Michael Hutchinson [xbuild] Fix dependency in C# targets
c197478 Michael Hutchinson [xbuild] Fix 2.0 tests to handle mcs sdk argument
693176c Michael Hutchinson [xbuild] Fix Tooltask.ToolPath behaviour to
match .NET
df52831 Michael Hutchinson [xbuild] Make ToolLocationHelper work better for
2.0/3.5
a55c588 Michael Hutchinson [xbuild] Fix typo that broke 2.0/3.5 targets
c705849 Michael Hutchinson [xbuild] Fix mscorlib resolution for custom
frameworks

So, is this a bug in xbuild?

Thank you

Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20140215/f74afbbc/attachment.html>