Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Platform needs to be either x64 or x86 to support Skia in Windows. #44

Closed
pauldendulk opened this issue Mar 15, 2016 · 6 comments
Closed
Milestone

Comments

@pauldendulk
Copy link

When compiling Skia.WindowsDesktop.Demo with Visual Studio 2015 update 1 on Windows 8.1 I get the compile error 'The Platform needs to be either x64 or x86 to support Skia in Windows.'. What is going on?

@pauldendulk
Copy link
Author

Simply select one of the alternative profiles from the compile targets dropdown, like 'Debug|x86'. Perhaps the 'Release' and 'Debug' targets could be removed.

@KvanTTT
Copy link

KvanTTT commented Apr 21, 2016

Adding new Platform x64 in Configuration Manager solved my same issue.

@tdoneal
Copy link

tdoneal commented Feb 7, 2017

I mean, why doesn't it just default to whatever the compiler is using if not specified? Or at minimum, it should default to x86...

@mattleibow
Copy link
Contributor

mattleibow commented Feb 7, 2017

This is related to #190

The latest changes make a choice to use the native bits that the platform specifies (and just copies both for AnyCPU), but at an app level, the platform needs to be specified.

On your point of picking the default (aka, pick x86 or x64), we might be able to do something like that... I am just preparing to release the next version, but maybe I can fit this in:

How does adding a MSBuild property in the csproj sound? So, we can still target AnyCPU, but if there is something like this:

<OverrideSkiaSharpPlatform>x86</OverrideSkiaSharpPlatform>

then, instead of copying both platforms to the output location, it just pretends it is an x86 app?

@mattleibow mattleibow reopened this Feb 7, 2017
@mattleibow mattleibow reopened this Feb 7, 2017
@tdoneal
Copy link

tdoneal commented Feb 8, 2017

I don't understand MSBuild at all, so I won't comment there. I would just say it's worth it to not have to google an error message and waste time fixing configuration issues. So whatever makes it "just work" is likely best (in my humble opinion).

@mattleibow
Copy link
Contributor

Closing this as I have added logic to try and detect the correct libraries to copy with AnyCPU.

@mattleibow mattleibow added this to the 1.56.2 milestone Feb 28, 2017
@ghost ghost locked as resolved and limited conversation to collaborators Aug 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants