Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Edward Ned Harvey (mono)
From: mono-devel-list-boun...@lists.ximian.com [mailto:mono-devel-list- boun...@lists.ximian.com] On Behalf Of David Curylo If you edit the .csproj file, you can have a platform-specific reference Mono.Posix like this: Reference Include=Mono.Posix Condition= '$(OS)' != 'Windows_NT' /

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread David Curylo
You have to use conditional compilation for the code that uses the conditional reference, in this case Mono.Posix. The reference appears with a warning in Visual Studio and you get a compiler warning, “The referenced component ‘Mono.Posix’ could not be found” but this is to be expected on

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Greg Young
The reference appears with a warning in Visual Studio and you get a compiler warning, “The referenced component ‘Mono.Posix’ could not be found” but this is to be expected on Windows/.NET. hmm we use warnings as errors will need to try this On Tue, Jan 6, 2015 at 4:54 PM, David Curylo

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Rafael Teixeira
Edward, Perhaps using the Message ... task to output the current value to the logging output, by default the console... On Tue, Jan 6, 2015, 18:11 Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: From: Dave Curylo [mailto:dacur...@gmail.com] On Behalf Of David Curylo

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Edward Ned Harvey (mono)
From: Dave Curylo [mailto:dacur...@gmail.com] On Behalf Of David Curylo You're right.I didn't realize that was what's going on.  It looks like conditional references need some hand holding like this: Choose When Condition= '$(OS)' == 'Unix' ItemGroup Reference

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Alexander Köplinger
Yeah, though you should be able to switch that off with CopyLocal=false in the Reference (haven't tested if you can apply a condition on that). For me, the burden of having multiple .csproj files would outweigh a simple cleanup of undesired DLLs, but that's of course different for everyone :) --

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Alexander Köplinger
There is a way to set a breakpoint with VS, though it's unsupported: http://blogs.msdn.com/b/visualstudio/archive/2010/07/06/debugging-msbuild-script-with-visual-studio.aspx Mono docs about the OS variable: The default environment variable ‘OS’ is set to “Windows_NT” on all currently supported

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread David Curylo
On Jan 6, 2015, at 2:57 PM, Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: Previously, you had a value 'Windows_NT' and now you have a value 'Unix' in there. How do you figure out what values are valid? I presume there's no such thing as setting a breakpoint inside

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Edward Ned Harvey (mono)
From: Dave Curylo [mailto:dacur...@gmail.com] On Behalf Of David Curylo You have to use conditional compilation for the code that uses the conditional reference, in this case Mono.Posix. The reference appears with a warning in Visual Studio and you get a compiler warning, The referenced

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread David Curylo
On Jan 6, 2015, at 11:12 AM, Edward Ned Harvey (mono) edward.harvey.m...@clevertrove.com wrote: The reason it works is because of the #if __MonoCS__ which eliminates any calls to the missing assembly. You’re right…I didn’t realize that was what’s going on. It looks like conditional

Re: [Mono-dev] Mono.Posix Cross Compiling

2015-01-06 Thread Timotheus Pokorra
Hello, As far as I can tell, any attempt to use Conditional property in the Reference tag is simply ignored. So I settle on using the kludgy hack of using different csproj files on windows mono. It works so I didn't spend more time on it - but if there's a more elegant solution, I'd