Nezz
1
I encounter the following error when I try to build with Monogame in Debug:
2> Adding obj\Debug_library_projects_\MonoGame.Framework\native_library_imports\armeabi-v7a\libopenal32.so
2> Adding obj\Debug_library_projects_\MonoGame.Framework.Net\native_library_imports\armeabi-v7a\libopenal32.so
2> Adding obj\Debug_library_projects_\MonoGame.Framework\native_library_imports\armeabi\libopenal32.so
2> Adding obj\Debug_library_projects_\MonoGame.Framework.Net\native_library_imports\armeabi\libopenal32.so
2> Adding obj\Debug_library_projects_\MonoGame.Framework\native_library_imports\x86\libopenal32.so
2> Adding obj\Debug_library_projects_\MonoGame.Framework.Net\native_library_imports\x86\libopenal32.so
2>The “BuildApk” task failed unexpectedly.
2>System.ArgumentException: An item with the same key has already been added.
Has anyone encountered something like this?
Nezz
2
This seems to be the culprit in MonoGame.Framework.Android.csproj:
<ItemGroup>
<EmbeddedNativeLibrary Include="..\ThirdParty\Dependencies\openal-soft\libs\armeabi-v7a\libopenal32.so">
<Platforms>Android,Ouya</Platforms>
<Link>libs\armeabi-v7a\libopenal32.so</Link>
</EmbeddedNativeLibrary>
<EmbeddedNativeLibrary Include="..\ThirdParty\Dependencies\openal-soft\libs\armeabi\libopenal32.so">
<Platforms>Android,Ouya</Platforms>
<Link>libs\armeabi\libopenal32.so</Link>
</EmbeddedNativeLibrary>
<EmbeddedNativeLibrary Include="..\ThirdParty\Dependencies\openal-soft\libs\x86\libopenal32.so">
<Platforms>Android,Ouya</Platforms>
<Link>libs\x86\libopenal32.so</Link>
</EmbeddedNativeLibrary>
</ItemGroup>
Why is MonoGame.Framework.Net trying to link it again, resulting in a conflict?
Nezz
3
Created an issue @GitHub:
Thanks for this guys I have been stuck on this for weeks. My fix(ok bodge) was to alter the .net project to build to bin/AndroidMFN and it worked.
I too have raised this with Xamarin and the reply was a deafening zero. Am I the only person getting fed up with there no support and unusable IDE??