Richard Peck

Results 47 comments of Richard Peck

I've uploaded my code to my forked repository (`windows` branch): https://github.com/richpeck/ruby2d/tree/windows There are quite a few bugs/issues with respect to the MRuby implementation, which I will work through tomorrow or...

### MSYS2 Repositories This is not essential - the key is installing MRuby, Simple2D etc. I used the following repositories: - - [Ruby](https://packages.msys2.org/package/mingw-w64-x86_64-ruby) - [MRuby](https://packages.msys2.org/package/mingw-w64-x86_64-mruby?repo=mingw64) - [SDL2](https://packages.msys2.org/package/mingw-w64-x86_64-SDL2?repo=mingw64) - [SDL2_TTF](https://packages.msys2.org/package/mingw-w64-x86_64-SDL2_ttf?repo=mingw64) -...

### build.rb This is the file which receives the build command from the cli (`ruby2d build --native ....`). [Line `101`](https://github.com/richpeck/ruby2d/blob/windows/lib/ruby2d/cli/build.rb#L101) is where the compiler is called for the native build....

### ruby2d.c This was a big problem and I am not sure if I have fixed it correctly. The errors we saw in the build/compile were caused by the mixing...

### ruby2d.rb This was to get the code to build in the native environment. There were some errors, such as the [following](https://github.com/richpeck/ruby2d/blob/windows/lib/ruby2d/window.rb#L261): - ``` def add(o) case o when nil...

### DLLs Finally, if you want to run the built code on another Windows system, you should copy the DLL files located in `[/assets/mingw/bin](https://github.com/ruby2d/assets/tree/a4e14729c37422f3bf482901d9faefde1aab3b61/mingw/bin)` into the runtime folder of the...

I had to change `ruby.c` substantially due to the errors which were showing. Remember, I was building on Windows, so we'll have to figure out how to get it to...

I'll see if I can get ahold of an ArchLinux instance and do some testing for you. Rich

Yes it does > On 2 July 2020 14:52 Reza Piri wrote: > > > > > Does this library have an open source license? I couldn't find one. >...

VERY interesting. The gem itself just uses all rails' native functionality... so I don't see why it would cause 100mb of memory usage. Are there any deeper reports you have...