SDL2# - C# Wrapper for SDL2
Go to file
2023-05-21 12:49:57 +09:00
.github/workflows Remove one unnecessary mkdir invocation 2023-03-08 18:13:40 +09:00
linux-build Check out SDL sources only once 2020-05-06 16:07:55 -04:00
native Merge remote-tracking branch 'upstream/update-osx-arm64-binaries' 2023-05-21 12:49:57 +09:00
src Bump projects to .NET 6 and add DllImport resolver for iOS 2023-03-08 11:51:55 +03:00
.gitignore Update .gitignore 2014-05-31 19:55:44 -04:00
app.config SDL2_gfx dllmap 2021-12-17 13:00:14 -05:00
appveyor.yml Bump AppVeyor image 2023-03-08 11:59:01 +03:00
LICENSE Happy New Year! 2021-01-01 11:32:54 -05:00
README SDL2# now supports SDL2_gfx! 2021-12-17 13:00:55 -05:00
SDL2-CS.csproj Bump projects to .NET 6 and add DllImport resolver for iOS 2023-03-08 11:51:55 +03:00
SDL2-CS.sln Change SDL2# project names. 2013-11-04 14:51:28 -05:00

This is SDL2#, a C# wrapper for SDL2.

Project Website: https://github.com/flibitijibibo/SDL2-CS

License
-------
SDL2 and SDL2# are released under the zlib license. See LICENSE for details.

About SDL2
----------
For more information about SDL2, visit the SDL wiki:

http://wiki.libsdl.org/moin.fcg/FrontPage

About the C# Wrapper
--------------------
The C# wrapper was written to be used for FNA's platform support. However, this
is written in a way that can be used for any general C# application.

The wrapper provides bindings for the following libraries:
- SDL2
- SDL2_gfx
- SDL2_image
- SDL2_mixer
- SDL2_ttf

Note that SDL2# will not provide every single SDL2 function. This is due to
limitations in the C# language that would cause major conflicts with the native
SDL2 library and its extensions.

SDL2# is a pure port of the C headers. The naming schemes for this library will
be exactly as they are done in the C library, with little-to-no concern for
"appropriate" C# style. The namespace indicates that this is SDL2, the class
names will indicate which library file the function/type/value exists in, and
everything else will be as close to the C version as technically possible.

About the Visual Studio Debugger
--------------------------------
When running C# applications under the Visual Studio debugger, native code that
names threads with the 0x406D1388 exception will silently exit. To prevent this
exception from being thrown by SDL, add this line before your SDL_Init call:

SDL.SDL_SetHint(SDL.SDL_HINT_WINDOWS_DISABLE_THREAD_NAMING, "1");