2
0
mirror of https://github.com/raylib-cs/raylib-cs synced 2025-04-03 11:09:40 -04:00

10 Commits

Author SHA1 Message Date
c8ddc440bb Updated Build platforms
For upcoming NuGet support
2020-05-02 04:27:16 +10:00
def2598e05 Moving Physac and Raygui into their own libraries and marking them as experimental.
- Both bindings have causes confusion and issues in project setup. Moving them into separate libraries should make things clearer and easier to maintain.
2020-04-28 20:53:45 +01:00
81f7a984f6 Changed Raylib-cs.csproj to only target netstandard2.0.
- Changed Raylib-cs.proj to use just one target framework.
- Removed targets net47 and netcoreapp3.1 from Raylib-cs.csproj.
- Removed netcoreapp3.1 from dotnetcore.yml workflow.
2020-04-07 20:41:22 +01:00
c79590c56c Added Raylib-cs.csproj.
- Testing multi-target options. Hopefully won't be needed with .NET 5.
Some issues getting multi-targeting to work well with OmniSharp in other projects so I may change this.
2020-04-01 14:50:00 +01:00
2995318a4e Project tidying
- Project now uses AnyCPU.
- Fixed assembly info and renamed Raylib-cs project to Generator.
- Removed resources folder and dlls.
- Improving current manual bindings.
2018-08-04 21:04:02 +01:00
a796df379b Separated example from generator
- Renamed Raylib-example to ExampleApplication.
- Example removed from Raylib-cs. It now only contains the generator. Use the current bindings in ExampleApplication/Raylib-cs.
2018-07-31 13:33:19 +01:00
759a652501 Added raylib-example project
- Separate project to test raylib on its own.
-
2018-07-28 09:26:59 +01:00
2d18c1a859 Renamed raylib.cs to raylib-manual.cs
- Making it clear this is the testing file for manually binding.
- Trying to move the project to use cppsharp generated bindings instead.
2018-07-26 15:46:10 +01:00
e0d590b855 Testing the idea of generating the bindings
- Added cppsharp to see if it will work with raylib.
2018-07-23 20:27:07 +01:00
7b965906f8 Added vs project
- Initial version of bindings(WIP)
2018-07-13 14:55:07 +01:00