When compiling a Unity project in VS 2013 I get the following compile warning:
warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "GameSparksUtils", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
Does the GameSparksUtils dll actually have an x86 dependancy? In which case, are there plans to make a dll version for iOS? Or does it just need its compile settings changed to be "Any CPU"? I've been running GameSparks on iOS without difficulties so far, but I may just be not using the functionality that depends on the x86 architecture so far.
Best Answer
C
Customer Support
said
over 8 years ago
Bobby. Thanks for the heads up. This will be addressed in the next update to the SDK which will be available imminently. In the meantime, as its a warning, it should all work ok if you ignore for now.
John.
1 Comment
Customer Support
said
over 8 years ago
Answer
Bobby. Thanks for the heads up. This will be addressed in the next update to the SDK which will be available imminently. In the meantime, as its a warning, it should all work ok if you ignore for now.
Bobby Wilkinson
When compiling a Unity project in VS 2013 I get the following compile warning:
Does the GameSparksUtils dll actually have an x86 dependancy? In which case, are there plans to make a dll version for iOS? Or does it just need its compile settings changed to be "Any CPU"? I've been running GameSparks on iOS without difficulties so far, but I may just be not using the functionality that depends on the x86 architecture so far.
Bobby. Thanks for the heads up. This will be addressed in the next update to the SDK which will be available imminently. In the meantime, as its a warning, it should all work ok if you ignore for now.
John.
Customer Support
Bobby. Thanks for the heads up. This will be addressed in the next update to the SDK which will be available imminently. In the meantime, as its a warning, it should all work ok if you ignore for now.
John.
-
Documentation Notes
-
Design issues with user events
-
Using NoSQL
-
Runtime Collections vs Metadata Collections
-
Anonymous authentication from browser app
-
Modules
-
Movement With Unity
-
Problem with url parameters for downloadables
-
Querying NoSql GameSparks database
-
Challenge accesType
See all 2487 topics