author Sam Lantinga
Wed, 28 Sep 2016 22:24:01 -0700
changeset 10375 9cf405a99347
parent 10171 5b61e12c0a30
child 10486 5bf595c48fd4
permissions -rw-r--r--
Updated version to 2.0.5 in preparation for release
     1 WinRT
     2 =====
     4 This port allows SDL applications to run on Microsoft's platforms that require
     5 use of "Windows Runtime", aka. "WinRT", APIs.  Microsoft may, in some cases,
     6 refer to them as either "Windows Store", or for Windows 10, "UWP" apps.
     8 Some of the operating systems that include WinRT, are:
    10 * Windows 10, via its Universal Windows Platform (UWP) APIs
    11 * Windows 8.x
    12 * Windows RT 8.x (aka. Windows 8.x for ARM processors)
    13 * Windows Phone 8.x
    16 Requirements
    17 ------------
    19 * Microsoft Visual C++ (aka Visual Studio), either 2015, 2013, or 2012
    20   - Free, "Community" or "Express" editions may be used, so long as they
    21     include  support for either "Windows Store" or "Windows Phone" apps.
    22     "Express" versions marked as supporting "Windows Desktop" development
    23     typically do not include support for creating WinRT apps, to note.
    24     (The "Community" editions of Visual C++ do, however, support both
    25     desktop/Win32 and WinRT development).
    26   - Visual C++ 2012 can only build apps that target versions 8.0 of Windows,
    27     or  Windows Phone.  8.0-targetted apps will run on devices running 8.1
    28     editions of Windows, however they will not be able to take advantage of
    29     8.1-specific features.
    30   - Visual C++ 2013 cannot create app projects that target Windows 8.0.
    31     Visual C++ 2013 Update 4, can create app projects for Windows Phone 8.0,
    32     Windows Phone 8.1, and Windows 8.1, but not Windows 8.0.  An optional
    33     Visual Studio add-in, "Tools for Maintaining Store apps for Windows 8",
    34     allows Visual C++ 2013 to load and build Windows 8.0 projects that were
    35     created with Visual C++ 2012, so long as Visual C++ 2012 is installed
    36     on the same machine.  More details on targeting different versions of
    37     Windows can found at the following web pages:
    38       - [Develop apps by using Visual Studio 2013](
    39       - [To add the Tools for Maintaining Store apps for Windows 8](
    40 * A valid Microsoft account - This requirement is not imposed by SDL, but
    41   rather by Microsoft's Visual C++ toolchain.  This is required to launch or 
    42   debug apps.
    45 Status
    46 ------
    48 Here is a rough list of what works, and what doens't:
    50 * What works:
    51   * compilation via Visual C++ 2012 through 2015
    52   * compile-time platform detection for SDL programs.  The C/C++ #define,
    53     `__WINRT__`, will be set to 1 (by SDL) when compiling for WinRT.
    54   * GPU-accelerated 2D rendering, via SDL_Renderer.
    55   * OpenGL ES 2, via the ANGLE library (included separately from SDL)
    56   * software rendering, via either SDL_Surface (optionally in conjunction with
    57     SDL_GetWindowSurface() and SDL_UpdateWindowSurface()) or via the
    58     SDL_Renderer APIs
    59   * threads
    60   * timers (via SDL_GetTicks(), SDL_AddTimer(), SDL_GetPerformanceCounter(),
    61     SDL_GetPerformanceFrequency(), etc.)
    62   * file I/O via SDL_RWops
    63   * mouse input  (unsupported on Windows Phone)
    64   * audio, via a modified version of SDL's XAudio2 backend
    65   * .DLL file loading.  Libraries *MUST* be packaged inside applications.  Loading
    66     anything outside of the app is not supported.
    67   * system path retrieval via SDL's filesystem APIs
    68   * game controllers.  Support is provided via the SDL_Joystick and
    69     SDL_GameController APIs, and is backed by Microsoft's XInput API.
    70   * multi-touch input
    71   * app events.  SDL_APP_WILLENTER* and SDL_APP_DIDENTER* events get sent out as
    72     appropriate.
    73   * window events
    74   * using Direct3D 11.x APIs outside of SDL.  Non-XAML / Direct3D-only apps can
    75     choose to render content directly via Direct3D, using SDL to manage the
    76     internal WinRT window, as well as input and audio.  (Use
    77     SDL_GetWindowWMInfo() to get the WinRT 'CoreWindow', and pass it into
    78     IDXGIFactory2::CreateSwapChainForCoreWindow() as appropriate.)
    80 * What partially works:
    81   * keyboard input.  Most of WinRT's documented virtual keys are supported, as
    82     well as many keys with documented hardware scancodes.  Converting
    83     SDL_Scancodes to or from SDL_Keycodes may not work, due to missing APIs
    84     (MapVirualKey()) in Microsoft's Windows Store / UWP APIs.
    85   * SDLmain.  WinRT uses a different signature for each app's main() function.
    86     SDL-based apps that use this port must compile in SDL_winrt_main_NonXAML.cpp
    87     (in `SDL\src\main\winrt\`) directly in order for their C-style main()
    88     functions to be called.
    90 * What doesn't work:
    91   * compilation with anything other than Visual C++
    92   * programmatically-created custom cursors.  These don't appear to be supported
    93     by WinRT.  Different OS-provided cursors can, however, be created via
    94     SDL_CreateSystemCursor() (unsupported on Windows Phone)
    95   * SDL_WarpMouseInWindow() or SDL_WarpMouseGlobal().  This are not currently
    96     supported by WinRT itself.
    97   * joysticks and game controllers that aren't supported by Microsoft's XInput
    98     API.
    99   * turning off VSync when rendering on Windows Phone.  Attempts to turn VSync
   100     off on Windows Phone result either in Direct3D not drawing anything, or it
   101     forcing VSync back on.  As such, SDL_RENDERER_PRESENTVSYNC will always get
   102     turned-on on Windows Phone.  This limitation is not present in non-Phone
   103     WinRT (such as Windows 8.x), where turning off VSync appears to work.
   104   * probably anything else that's not listed as supported
   108 Upgrade Notes
   109 -------------
   111 #### SDL_GetPrefPath() usage when upgrading WinRT apps from SDL 2.0.3
   113 SDL 2.0.4 fixes two bugs found in the WinRT version of SDL_GetPrefPath().
   114 The fixes may affect older, SDL 2.0.3-based apps' save data.  Please note
   115 that these changes only apply to SDL-based WinRT apps, and not to apps for
   116 any other platform.
   118 1. SDL_GetPrefPath() would return an invalid path, one in which the path's
   119    directory had not been created.  Attempts to create files there
   120    (via fopen(), for example), would fail, unless that directory was
   121    explicitly created beforehand.
   123 2. SDL_GetPrefPath(), for non-WinPhone-based apps, would return a path inside
   124    a WinRT 'Roaming' folder, the contents of which get automatically
   125    synchronized across multiple devices.  This process can occur while an
   126    application runs, and can cause existing save-data to be overwritten
   127    at unexpected times, with data from other devices.  (Windows Phone apps
   128    written with SDL 2.0.3 did not utilize a Roaming folder, due to API
   129    restrictions in Windows Phone 8.0).
   132 SDL_GetPrefPath(), starting with SDL 2.0.4, addresses these by:
   134 1. making sure that SDL_GetPrefPath() returns a directory in which data
   135    can be written to immediately, without first needing to create directories.
   137 2. basing SDL_GetPrefPath() off of a different, non-Roaming folder, the
   138    contents of which do not automatically get synchronized across devices
   139    (and which require less work to use safely, in terms of data integrity).
   141 Apps that wish to get their Roaming folder's path can do so either by using
   142 SDL_WinRTGetFSPathUTF8(), SDL_WinRTGetFSPathUNICODE() (which returns a
   143 UCS-2/wide-char string), or directly through the WinRT class,
   144 Windows.Storage.ApplicationData.
   148 Setup, High-Level Steps
   149 -----------------------
   151 The steps for setting up a project for an SDL/WinRT app looks like the
   152 following, at a high-level:
   154 1. create a new Visual C++ project using Microsoft's template for a,
   155    "Direct3D App".
   156 2. remove most of the files from the project.
   157 3. make your app's project directly reference SDL/WinRT's own Visual C++
   158    project file, via use of Visual C++'s "References" dialog.  This will setup
   159    the linker, and will copy SDL's .dll files to your app's final output.
   160 4. adjust your app's build settings, at minimum, telling it where to find SDL's
   161    header files.
   162 5. add files that contains a WinRT-appropriate main function, along with some
   163    data to make sure mouse-cursor-hiding (via SDL_ShowCursor(SDL_DISABLE) calls)
   164    work properly.
   165 6. add SDL-specific app code.
   166 7. build and run your app.
   169 Setup, Detailed Steps
   170 ---------------------
   172 ### 1. Create a new project ###
   174 Create a new project using one of Visual C++'s templates for a plain, non-XAML,
   175 "Direct3D App" (XAML support for SDL/WinRT is not yet ready for use).  If you
   176 don't see one of these templates, in Visual C++'s 'New Project' dialog, try
   177 using the textbox titled, 'Search Installed Templates' to look for one.
   180 ### 2. Remove unneeded files from the project ###
   182 In the new project, delete any file that has one of the following extensions:
   184 - .cpp
   185 - .h
   186 - .hlsl
   188 When you are done, you should be left with a few files, each of which will be a
   189 necessary part of your app's project.  These files will consist of:
   191 - an .appxmanifest file, which contains metadata on your WinRT app.  This is
   192   similar to an Info.plist file on iOS, or an AndroidManifest.xml on Android.
   193 - a few .png files, one of which is a splash screen (displayed when your app
   194   launches), others are app icons.
   195 - a .pfx file, used for code signing purposes.
   198 ### 3. Add references to SDL's project files ###
   200 SDL/WinRT can be built in multiple variations, spanning across three different
   201 CPU architectures (x86, x64, and ARM) and two different configurations
   202 (Debug and Release).  WinRT and Visual C++ do not currently provide a means
   203 for combining multiple variations of one library into a single file.
   204 Furthermore, it does not provide an easy means for copying pre-built .dll files
   205 into your app's final output (via Post-Build steps, for example).  It does,
   206 however, provide a system whereby an app can reference the MSVC projects of
   207 libraries such that, when the app is built:
   209 1. each library gets built for the appropriate CPU architecture(s) and WinRT
   210    platform(s).
   211 2. each library's output, such as .dll files, get copied to the app's build 
   212    output.
   214 To set this up for SDL/WinRT, you'll need to run through the following steps:
   216 1. open up the Solution Explorer inside Visual C++ (under the "View" menu, then
   217    "Solution Explorer")
   218 2. right click on your app's solution.
   219 3. navigate to "Add", then to "Existing Project..."
   220 4. find SDL/WinRT's Visual C++ project file and open it.  Different project
   221    files exist for different WinRT platforms.  All of them are in SDL's
   222    source distribution, in the following directories:
   223     * `VisualC-WinRT/UWP_VS2015/`        - for Windows 10 / UWP apps
   224     * `VisualC-WinRT/WinPhone81_VS2013/` - for Windows Phone 8.1 apps
   225     * `VisualC-WinRT/WinRT80_VS2012/`    - for Windows 8.0 apps
   226     * `VisualC-WinRT/WinRT81_VS2013/`    - for Windows 8.1 apps
   227 5. once the project has been added, right-click on your app's project and
   228    select, "References..."
   229 6. click on the button titled, "Add New Reference..."
   230 7. check the box next to SDL
   231 8. click OK to close the dialog
   232 9. SDL will now show up in the list of references.  Click OK to close that
   233    dialog.
   235 Your project is now linked to SDL's project, insofar that when the app is
   236 built, SDL will be built as well, with its build output getting included with
   237 your app.
   240 ### 4. Adjust Your App's Build Settings ###
   242 Some build settings need to be changed in your app's project.  This guide will
   243 outline the following:
   245 - making sure that the compiler knows where to find SDL's header files
   246 - **Optional for C++, but NECESSARY for compiling C code:** telling the
   247   compiler not to use Microsoft's C++ extensions for WinRT development.
   248 - **Optional:** telling the compiler not generate errors due to missing
   249   precompiled header files.
   251 To change these settings:
   253 1. right-click on the project
   254 2. choose "Properties"
   255 3. in the drop-down box next to "Configuration", choose, "All Configurations"
   256 4. in the drop-down box next to "Platform", choose, "All Platforms"
   257 5. in the left-hand list, expand the "C/C++" section
   258 6. select "General"
   259 7. edit the "Additional Include Directories" setting, and add a path to SDL's
   260    "include" directory
   261 8. **Optional: to enable compilation of C code:** change the setting for
   262    "Consume Windows Runtime Extension" from "Yes (/ZW)" to "No".  If you're 
   263    working with a completely C++ based project, this step can usually be 
   264    omitted.
   265 9. **Optional: to disable precompiled headers (which can produce 
   266    'stdafx.h'-related build errors, if setup incorrectly:** in the left-hand 
   267    list, select "Precompiled Headers", then change the setting for "Precompiled 
   268    Header" from "Use (/Yu)" to "Not Using Precompiled Headers".
   269 10. close the dialog, saving settings, by clicking the "OK" button
   272 ### 5. Add a WinRT-appropriate main function, and a blank-cursor image, to the app. ###
   274 A few files should be included directly in your app's MSVC project, specifically:
   275 1. a WinRT-appropriate main function (which is different than main() functions on
   276    other platforms)
   277 2. a Win32-style cursor resource, used by SDL_ShowCursor() to hide the mouse cursor
   278    (if and when the app needs to do so).  *If this cursor resource is not
   279    included, mouse-position reporting may fail if and when the cursor is
   280    hidden, due to possible bugs/design-oddities in Windows itself.*
   282 To include these files:
   284 1. right-click on your project (again, in Visual C++'s Solution Explorer), 
   285    navigate to "Add", then choose "Existing Item...".
   286 2. navigate to the directory containing SDL's source code, then into its
   287    subdirectory, 'src/main/winrt/'.  Select, then add, the following files:
   288    - `SDL_winrt_main_NonXAML.cpp`
   289    - `SDL2-WinRTResources.rc`
   290    - `SDL2-WinRTResource_BlankCursor.cur`
   291 3. right-click on the file `SDL_winrt_main_NonXAML.cpp` (as listed in your
   292    project), then click on "Properties...".
   293 4. in the drop-down box next to "Configuration", choose, "All Configurations"
   294 5. in the drop-down box next to "Platform", choose, "All Platforms"
   295 6. in the left-hand list, click on "C/C++"
   296 7. change the setting for "Consume Windows Runtime Extension" to "Yes (/ZW)".
   297 8. click the OK button.  This will close the dialog.
   300 **NOTE: C++/CX compilation is currently required in at least one file of your 
   301 app's project.  This is to make sure that Visual C++'s linker builds a 'Windows 
   302 Metadata' file (.winmd) for your app.  Not doing so can lead to build errors.**
   305 ### 6. Add app code and assets ###
   307 At this point, you can add in SDL-specific source code.  Be sure to include a 
   308 C-style main function (ie: `int main(int argc, char *argv[])`).  From there you 
   309 should be able to create a single `SDL_Window` (WinRT apps can only have one 
   310 window, at present), as well as an `SDL_Renderer`.  Direct3D will be used to 
   311 draw content.  Events are received via SDL's usual event functions 
   312 (`SDL_PollEvent`, etc.)  If you have a set of existing source files and assets, 
   313 you can start adding them to the project now.  If not, or if you would like to 
   314 make sure that you're setup correctly, some short and simple sample code is 
   315 provided below.
   318 #### 6.A. ... when creating a new app ####
   320 If you are creating a new app (rather than porting an existing SDL-based app), 
   321 or if you would just like a simple app to test SDL/WinRT with before trying to 
   322 get existing code working, some working SDL/WinRT code is provided below.  To 
   323 set this up:
   325 1. right click on your app's project
   326 2. select Add, then New Item.  An "Add New Item" dialog will show up.
   327 3. from the left-hand list, choose "Visual C++"
   328 4. from the middle/main list, choose "C++ File (.cpp)"
   329 5. near the bottom of the dialog, next to "Name:", type in a name for your 
   330 source file, such as, "main.cpp".
   331 6. click on the Add button.  This will close the dialog, add the new file to 
   332 your project, and open the file in Visual C++'s text editor.
   333 7. Copy and paste the following code into the new file, then save it.
   336     #include <SDL.h>
   338     int main(int argc, char **argv)
   339     {
   340         SDL_DisplayMode mode;
   341         SDL_Window * window = NULL;
   342         SDL_Renderer * renderer = NULL;
   343         SDL_Event evt;
   345         if (SDL_Init(SDL_INIT_VIDEO) != 0) {
   346             return 1;
   347         }
   349         if (SDL_GetCurrentDisplayMode(0, &mode) != 0) {
   350             return 1;
   351         }
   353         if (SDL_CreateWindowAndRenderer(mode.w, mode.h, SDL_WINDOW_FULLSCREEN, &window, &renderer) != 0) {
   354             return 1;
   355         }
   357         while (1) {
   358             while (SDL_PollEvent(&evt)) {
   359             }
   361             SDL_SetRenderDrawColor(renderer, 0, 255, 0, 255);
   362             SDL_RenderClear(renderer);
   363             SDL_RenderPresent(renderer);
   364         }
   365     }
   368 #### 6.B. Adding code and assets ####
   370 If you have existing code and assets that you'd like to add, you should be able 
   371 to add them now.  The process for adding a set of files is as such.
   373 1. right click on the app's project
   374 2. select Add, then click on "New Item..."
   375 3. open any source, header, or asset files as appropriate.  Support for C and 
   376 C++ is available.
   378 Do note that WinRT only supports a subset of the APIs that are available to 
   379 Win32-based apps.  Many portions of the Win32 API and the C runtime are not 
   380 available.
   382 A list of unsupported C APIs can be found at 
   383 <>
   385 General information on using the C runtime in WinRT can be found at 
   386 <>
   388 A list of supported Win32 APIs for WinRT apps can be found at 
   389 <>.  To note, 
   390 the list of supported Win32 APIs for Windows Phone 8.0 is different.  
   391 That list can be found at 
   392 <>
   395 ### 7. Build and run your app ###
   397 Your app project should now be setup, and you should be ready to build your app.  
   398 To run it on the local machine, open the Debug menu and choose "Start 
   399 Debugging".  This will build your app, then run your app full-screen.  To switch 
   400 out of your app, press the Windows key.  Alternatively, you can choose to run 
   401 your app in a window.  To do this, before building and running your app, find 
   402 the drop-down menu in Visual C++'s toolbar that says, "Local Machine".  Expand 
   403 this by clicking on the arrow on the right side of the list, then click on 
   404 Simulator.  Once you do that, any time you build and run the app, the app will 
   405 launch in window, rather than full-screen.
   408 #### 7.A. Running apps on older, ARM-based, "Windows RT" devices ####
   410 **These instructions do not include Windows Phone, despite Windows Phone
   411 typically running on ARM processors.**  They are specifically for devices
   412 that use the "Windows RT" operating system, which was a modified version of
   413 Windows 8.x that ran primarily on ARM-based tablet computers.
   415 To build and run the app on ARM-based, "Windows RT" devices, you'll need to:
   417 - install Microsoft's "Remote Debugger" on the device.  Visual C++ installs and 
   418   debugs ARM-based apps via IP networks.
   419 - change a few options on the development machine, both to make sure it builds 
   420   for ARM (rather than x86 or x64), and to make sure it knows how to find the 
   421   Windows RT device (on the network).
   423 Microsoft's Remote Debugger can be found at 
   424 <>.  Please note 
   425 that separate versions of this debugger exist for different versions of Visual 
   426 C++, one each for MSVC 2015, 2013, and 2012.
   428 To setup Visual C++ to launch your app on an ARM device:
   430 1. make sure the Remote Debugger is running on your ARM device, and that it's on 
   431    the same IP network as your development machine.
   432 2. from Visual C++'s toolbar, find a drop-down menu that says, "Win32".  Click 
   433    it, then change the value to "ARM".
   434 3. make sure Visual C++ knows the hostname or IP address of the ARM device.  To 
   435    do this:
   436     1. open the app project's properties
   437     2. select "Debugging"
   438     3. next to "Machine Name", enter the hostname or IP address of the ARM 
   439        device
   440     4. if, and only if, you've turned off authentication in the Remote Debugger,
   441        then change the setting for "Require Authentication" to No
   442     5. click "OK"
   443 4. build and run the app (from Visual C++).  The first time you do this, a 
   444    prompt will show up on the ARM device, asking for a Microsoft Account.  You 
   445    do, unfortunately, need to log in here, and will need to follow the 
   446    subsequent registration steps in order to launch the app.  After you do so, 
   447    if the app didn't already launch, try relaunching it again from within Visual 
   448    C++.
   451 Troubleshooting
   452 ---------------
   454 #### Build fails with message, "error LNK2038: mismatch detected for 'vccorlib_lib_should_be_specified_before_msvcrt_lib_to_linker'"
   456 Try adding the following to your linker flags.  In MSVC, this can be done by
   457 right-clicking on the app project, navigating to Configuration Properties ->
   458 Linker -> Command Line, then adding them to the Additional Options
   459 section.
   461 * For Release builds / MSVC-Configurations, add:
   463     /nodefaultlib:vccorlib /nodefaultlib:msvcrt vccorlib.lib msvcrt.lib
   465 * For Debug builds / MSVC-Configurations, add:
   467     /nodefaultlib:vccorlibd /nodefaultlib:msvcrtd vccorlibd.lib msvcrtd.lib
   470 #### Mouse-motion events fail to get sent, or SDL_GetMouseState() fails to return updated values
   472 This may be caused by a bug in Windows itself, whereby hiding the mouse
   473 cursor can cause mouse-position reporting to fail.
   475 SDL provides a workaround for this, but it requires that an app links to a
   476 set of Win32-style cursor image-resource files.  A copy of suitable resource
   477 files can be found in `src/main/winrt/`.  Adding them to an app's Visual C++
   478 project file should be sufficient to get the app to use them.