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

Run .NET Realm Tests with wrappers built in win8.1 #2530

Closed
sync-by-unito bot opened this issue Jul 20, 2021 · 2 comments · Fixed by #2564
Closed

Run .NET Realm Tests with wrappers built in win8.1 #2530

sync-by-unito bot opened this issue Jul 20, 2021 · 2 comments · Fixed by #2564
Assignees

Comments

@sync-by-unito
Copy link

sync-by-unito bot commented Jul 20, 2021

Even though we target Win 8.1 API from Windows 10 OS, it seems that there are still uncovered issues when running the SDK on Windows 8.1. Because of this, trying to make a create a workflow dispatch to run once in a while where we manually install a Win8.1 SDK in Windows 10 and compile the wrappers. If that can't be achieved in a short amount of time 1/2 days, then it should be manually done in a win8.1 VM.

@sync-by-unito
Copy link
Author

sync-by-unito bot commented Jul 21, 2021

➤ Andrea Catalini commented:

Unfortunately, following the advice reported here, the output of dotnet --info doesn't show any change before and after the installation. Given the fact that the newer Windows 10 SDK supports the older 8.1 API, which is exactly what's allowing us to target Windows 8.1 from the latest version of Visual Studio 2019 (which uses Windows 10 SDK); the only thing left for me to do is to manually install VS 2015, which uses Windows 8.1 SDK, in a Windows 8.1 VM.
Note: I think that installing VS 2015 on Windows 10 may yield the same result, but just to be sure I used a Windows 8.1 installation.

@sync-by-unito
Copy link
Author

sync-by-unito bot commented Jul 23, 2021

➤ Andrea Catalini commented:

  • VS2019 doesn't have windows 8.1 SDK
  • In the post it's said to use VS2015, but that doesn't have "Visual C++ Tools for CMake", which is necessary to build our wrappers
  • VS2017 is the minimum requirement to have "Visual C++ Tools for CMake" but that necessarily brings in Win 10 sdk. VS2017 is the last version of VS that brings Win 8.1 SDK.
  • Unfortunately, the version of CMake brought by VS2017 is too old (it needs <= 3.15.0, but VS2017 brings 3.12.18081601-MSVC_2)
    Hence, I ended up installing VS2019 on Windows 8.1. However, I can't get it to build the wrappers as CMake keeps crashing even when asked to show the --help.

I need to ask to core if they have ever seen CMake behaving like this.

@sync-by-unito sync-by-unito bot assigned nirinchev and unassigned LaPeste Aug 18, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants