[Mono-dev] Recent xbuild fixes causing issues with finding mcs
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 br
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
On Sat, Feb 15, 2014 at 9:46 AM, Michael Franz wrote: > 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 > 6
Re: [Mono-dev] Strange Crash with mono-3.2.3 + Qt-5.2.1
The problem exists for the current master, and seem independent of the garbage collector choosen (incl. boehm/sgen/ext. boehm). -- View this message in context: http://mono.1490590.n4.nabble.com/Strange-Crash-with-mono-3-2-3-Qt-5-2-1-tp4661905p4661910.html Sent from the Mono - Dev mailing list archive at Nabble.com. ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Getting started on mono sources
While I am not positive on this at all, it may be easier to just use make in a cygwin env. On 02/15/2014 04:19 PM, jean-michel.perr...@csiro.au wrote: > Hi Edward, > > At least a couple of people including myself have an interest in > recommended dev env to work on Mono itself ( > http://lists.ximian.com/pipermail/mono-devel-list/2013-July/040638.html). > A Howto on recommended setup for Mono contributions would save a fair > bit of time and hassle for contributors, but I have not heard of such > a document. > > You should find a Visual Studio solution under /mono/msvc/scripts. The > Readme has some instructions as to how to re-generate solution and > project files if you so wish. > > A couple of years ago I updated the code that generates VS project and > solution files, with the intent to be able to navigate and compile > Mono C# in VS. You'll find related emails at > http://lists.ximian.com/pipermail/mono-devel-list/2012-May/038908.html > and http://lists.ximian.com/pipermail/mono-devel-list/2012-May/038875.html > While I originally aimed at developing and debugging with VS (in > particular to benefit from mixed-mode debugging) I renounced. I guess > this would require a revival of something like Mono tools for VS. > > I'd like to hear from you if you find an IDE and tools setup that > suits you. > > Cheers > > > *From:* mono-devel-list-boun...@lists.ximian.com > [mono-devel-list-boun...@lists.ximian.com] on behalf of Edward Ned > Harvey (mono) [edward.harvey.m...@clevertrove.com] > *Sent:* Saturday, February 15, 2014 1:11 PM > *To:* mono-devel-list@lists.ximian.com > *Subject:* [Mono-dev] Getting started on mono sources > > I'm a developer who uses mono and .NET a lot - and as such, I very > often want to read the mono source to see how something is > implemented. (Someday, I'll probably stumble across something that > should be improved.) > > > > Before anything else, I'd like to ask, is there a preferred platform > or IDE or something, for working on the mono source? Some "getting > started on mono development" document? Although I've downloaded > sources, it's not obvious to me, how to open in for example visual > studio, and become a useful human being. (Side note, I ran git clone > for several hours today, and eventually decided to just abort it and > download zip file.) > > > > At the moment, I would love to simply be able to open > mcs\class\System\System.Net.Security\SslStream.cs and see how it does > the handshake, negotiating protocols and key exchanges, etc. I would > *truly* love to launch code examples, and have the ability to step > through code, to actually observe its behavior. > > > > At present, I'm blindly trying to open things in VS, without a project > file or defintions of compiler symbols, and basically all the code is > grayed out. > > > > While I usually use VS, I'm happy to switch to a different IDE, if for > example, Xamarin Studio is "the preferred" platform to develop on. > The goal that I care about is being able to browse, edit, and > hopefully even build and debug code, as effectively as possible. > > > > Thanks for pointers... > > > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Getting started on mono sources
Hi Edward, At least a couple of people including myself have an interest in recommended dev env to work on Mono itself ( http://lists.ximian.com/pipermail/mono-devel-list/2013-July/040638.html). A Howto on recommended setup for Mono contributions would save a fair bit of time and hassle for contributors, but I have not heard of such a document. You should find a Visual Studio solution under /mono/msvc/scripts. The Readme has some instructions as to how to re-generate solution and project files if you so wish. A couple of years ago I updated the code that generates VS project and solution files, with the intent to be able to navigate and compile Mono C# in VS. You'll find related emails at http://lists.ximian.com/pipermail/mono-devel-list/2012-May/038908.html and http://lists.ximian.com/pipermail/mono-devel-list/2012-May/038875.html While I originally aimed at developing and debugging with VS (in particular to benefit from mixed-mode debugging) I renounced. I guess this would require a revival of something like Mono tools for VS. I'd like to hear from you if you find an IDE and tools setup that suits you. Cheers From: mono-devel-list-boun...@lists.ximian.com [mono-devel-list-boun...@lists.ximian.com] on behalf of Edward Ned Harvey (mono) [edward.harvey.m...@clevertrove.com] Sent: Saturday, February 15, 2014 1:11 PM To: mono-devel-list@lists.ximian.com Subject: [Mono-dev] Getting started on mono sources I'm a developer who uses mono and .NET a lot - and as such, I very often want to read the mono source to see how something is implemented. (Someday, I'll probably stumble across something that should be improved.) Before anything else, I'd like to ask, is there a preferred platform or IDE or something, for working on the mono source? Some "getting started on mono development" document? Although I've downloaded sources, it's not obvious to me, how to open in for example visual studio, and become a useful human being. (Side note, I ran git clone for several hours today, and eventually decided to just abort it and download zip file.) At the moment, I would love to simply be able to open mcs\class\System\System.Net.Security\SslStream.cs and see how it does the handshake, negotiating protocols and key exchanges, etc. I would *truly* love to launch code examples, and have the ability to step through code, to actually observe its behavior. At present, I'm blindly trying to open things in VS, without a project file or defintions of compiler symbols, and basically all the code is grayed out. While I usually use VS, I'm happy to switch to a different IDE, if for example, Xamarin Studio is "the preferred" platform to develop on. The goal that I care about is being able to browse, edit, and hopefully even build and debug code, as effectively as possible. Thanks for pointers... ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Getting started on mono sources
> From: Brandon Perry [mailto:bperry.volat...@gmail.com] > Sent: Saturday, February 15, 2014 5:34 PM > > While I am not positive on this at all, it may be easier to just use > make in a cygwin env. So, whether mac, linux, unix, or windows, the easiest way to build is clearly to use make. But for debugging purposes, and development of mono itself, aren't people using IDE's of some kind? Debugging would seem very cumbersome to me, without the IDE... Ability to step through code, examine runtime variables, etc... ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
AFAIK something's wrong with the installation if $prefix/lib/mono/4.5/mcs.exe is missing. What does your $prefix/bin/mcs point to? On 15 February 2014 10:51, Michael Franz wrote: > On Sat, Feb 15, 2014 at 9:46 AM, Michael Franz wrote: >> >> 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 somet
Re: [Mono-dev] Recent xbuild fixes causing issues with finding mcs
On Sat, Feb 15, 2014 at 10:02 PM, Michael Hutchinson < m.j.hutchin...@gmail.com> wrote: > AFAIK something's wrong with the installation if > $prefix/lib/mono/4.5/mcs.exe is missing. > > What does your $prefix/bin/mcs point to? > > It points to a binary that does not run on its own. bash-4.1$ ./lib/mono/4.5/mcs.exe --version bash: ./lib/mono/4.5/mcs.exe: cannot execute binary file but, if I run it with mono it will work. bash-4.1$ bin/mono ./lib/mono/4.5/mcs.exe --version Mono C# compiler version 3.2.7.0 Prior to the change, it was the mcs wrapper that was being executed, after the change, it is trying to run the .NET binary directly. The contents of mcs is: #!/bin/sh exec /opt/local/JenkinsBuilds/bin/mono $MONO_OPTIONS /opt/local/JenkinsBuilds/lib/mono/4.5/mcs.exe "$@" On 15 February 2014 10:51, Michael Franz wrote: > > On Sat, Feb 15, 2014 at 9:46 AM, Michael Franz > wrote: > >> > >> 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 sta
[Mono-dev] NUnit shadow copy and multiple users issue
Hi, I have been setting up my development environment on CentOS 6.5 and have had some great success. My latest issue is temp directories and shadow copies while running nunit. The issue is documented here and fixed in NUnit 3.0 https://bugs.launchpad.net/nunit-3.0/+bug/719187 . Is there any plan to upgrade the Mono version of NUnit? I might be wrong, but I have only been able to get the version of NUnit that is embedded in Mono to work for me. Is there a way that I can upgrade my local copy and have it still work? Or, is the best way to resolve this issue is to create a patch for the shadow copy logic for the Mono version of NUnit? Michael ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
