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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to build OpenSage.LowLevel without removing xamarinmac20 from targets? #17

Closed
paavohuhtala opened this issue Dec 25, 2017 · 3 comments

Comments

@paavohuhtala
Copy link
Contributor

paavohuhtala commented Dec 25, 2017

Self-explanatory title. I couldn't build the graphics DLL on Windows 10 without removing xamarinmac20 from <TargetFrameworks> in the .csproj. Do I need to install the Xamarin SDK or do something else to fix this properly? 馃

I'm the running the latest VS Enterprise with all recent .NET targeting packs installed.

@tgjones
Copy link
Collaborator

tgjones commented Dec 26, 2017

If you (somewhat unintuitively) choose the "Mobile development with .NET" workload in the Visual Studio Installer, you'll be able to build the xamarinmac20 target.

I can do some MSBuild trickery to exclude this target when building on Windows, but it's quite handy for my own development (on Windows) to keep it in, since it lets me see errors from both the D3D11 and Metal backends without even having to compile.

The ideal would be an MSBuild conditional thing to skip the xamarinmac20 target only if the Xamarin workload isn't installed. I'll look into that.

@paavohuhtala
Copy link
Contributor Author

Thanks! I installed the Xamarin component from the VS installer and it now builds with an unmodified csproj.

There's still a build warning

No Address and User has been specified in order to establish a connection to a Mac Server, so only the main assembly was compiled for project 'OpenSage.LowLevel'. Connect to a Mac Server and try again to build the full application.

but it doesn't prevent it from building.

Maybe this should be added to the readme?

@tgjones
Copy link
Collaborator

tgjones commented Jan 30, 2018

Fixed this by removing xamarinmac20 altogether...

@tgjones tgjones closed this as completed Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants