Uploaded image for project: 'Titanium SDK/CLI'
  1. Titanium SDK/CLI
  2. TIMOB-24959

Windows: Detect individual versions of Windows 10 SDKs

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: High
    • Resolution: Done
    • Affects Version/s: Release 6.2.0
    • Fix Version/s: None
    • Component/s: Tooling, Windows
    • Labels:
      None

      Description

      Description

      Currently when detecting Windows 10 SDKs we look for a registry key and then assign a generic '10.0' SDK with some info

      We can improve the individual SDK detection by following a similar method to one of the utility scripts called by VsDevCmd, C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\vsdevcmd\core\winsdk.bat

      That files basic flow when searching for an SDK is

      <registry_hive_path> is one of HKCU\SOFTWARE\Wow6432Node, HKLM\SOFTWARE, or HKCU\SOFTWARE

      1. Get the installation folder using {{reg query <regsitry_hive_path>\Microsoft\Microsoft SDKs\Windows\v10.0 /v "InstallationFolder"}
      2. Set to WindowsSdkDir
      3. For each directory in <WindowsSdkDir>\include
      • Look for <WindowsSdkDir>\include\<version>\um\Windows.h, if it exists it's a valid SDK

      I'm not sure what changes would be required to the SDK build process if we switched from using an generic 10.0 to individual SDKs

        Attachments

          Activity

            People

            • Assignee:
              kiguchi Kota Iguchi (Inactive)
              Reporter:
              eharris Ewan Harris
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Backbone Issue Sync

                • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                  Git Integration