[build] Make our MSBuild builder a 64bit process#6416
Conversation
|
/cc @jonpryor |
|
|
I think we still need the configuration property groups |
|
i think someone else who is not me should own this work item :p |
|
Hi! This is critical issue as we cannot sanely compile our stuff anymore! Can we please get some action on this so we can get it merged asap? |
Xamarin.Android is 64bit only now and will only allow you to compile Android projects if our hosted builder is also 64bit. Fixes VSTS #724560 - Make our MSBuild builder a 64bit process
dc63ca6 to
c00d55f
Compare
|
Updated the pull request. Not managed to verify this fixes the problem. Tried master Xamarin.Android 9.1.199-11 and 9.1.199-13 and Android projects build without errors when using VS Mac 7.6 and 7.7 without this change. Is there a way to see a build failure when using the 32-bit msbuild host? |
|
OK a repro is to use VS Mac 7.7, Xamarin.Android Xamarin.Android 9.1.199.11 (master) create and build an Android project. Build error occurs: |
|
Can verify that this PR allows VSMac to build with master Xamarin.Android 9.1.199-22 |
|
Hopefully, other msbuild tasks (i.e. nuget ones) ship 64bit native libs. Looks good to me! 👍 |
|
Shouldn't matter in the long run, as macOS is deprecating 32bit |
|
@mrward in the same vein I noticed that the NUnit test runners are also being executed on a 32bits process. I assume the fix needed is similar, do you want me to open a separate issue? |
|
@Therzok indeed although that PR seems to be handling both 32bits and 64bits cases, do we still want that or should it only be one runner that is 64bits only? |
On mac, sure. On other platforms, we need to keep that functionality, otherwise unit testing 32bit pinvokes will be broken. |
|
It looks like c# binding tests are hanging. |
|
@monojenkins backport release-7.7 |
Xamarin.Android is 64bit only now and will only allow you to compile
Android projects if our hosted builder is also 64bit.
Fixes VSTS 724560