Update README slightly

This commit is contained in:
Struma 2020-12-30 18:39:45 -05:00 committed by Roza
parent 5d4758edaa
commit 774b288a68
2 changed files with 5 additions and 4 deletions

View file

@ -24,17 +24,18 @@ This binding should support RGSS1, RGSS2 and RGSS3. Note that I've only tested t
* SDL2*
* SDL2_image
* SDL2_ttf
* [My Ruby 1.8 fork](https://gitlab.com/mkxp-z/ruby/-/tree/ruby_1_8_7), if using Ruby 1.8
* Ruby MRI (1.8.7, 1.9.3, 2.1-2.7, 3.0)
* vorbisfile
* pixman
* zlib
* openssl (for HTTPS, optional)
* OpenGL/ES
mkxp-z employs the meson build system, so you'll need to install that beforehand.
meson will use pkg-config to locate the respective include/library paths. If you installed any dependencies into non-standard prefixes, make sure to set `-Dpkg_config_path` accordingly when configuring the build. If pkgconfig cannot find a dependency, meson will attempt to use CMake scripts instead (if CMake is installed), followed by system installations/macOS frameworks.
Midi support is enabled by default and requires fluidsynth to be present at runtime (not needed for building); if mkxp can't find it at runtime, midi playback is disabled. It looks for `libfluidsynth.so.1` on Linux, `libfluidsynth.dylib.1` on OSX and `fluidsynth.dll` on Windows, so make sure to have one of these in your link path. If you still need fluidsynth to be hard linked at buildtime, use `-Dshared_fluid=true`. When building fluidsynth yourself, you can disable almost all options (audio drivers etc.) as they are not used. Note that upstream fluidsynth has support for sharing soundfont data between synthesizers (mkxp uses multiple synths), so if your memory usage is very high, you might want to try compiling fluidsynth from git master.
Midi support is enabled by default and requires fluidsynth to be present at runtime (not needed for building); if mkxp can't find it at runtime, midi playback is disabled. It looks for `libfluidsynth.so.3` on Linux and `fluidsynth.dll` on Windows, so make sure to have one of these in your link path. If you still need fluidsynth to be hard linked at buildtime, use `-Dshared_fluid=true`. When building fluidsynth yourself, you can disable almost all options (audio drivers etc.) as they are not used. Note that upstream fluidsynth has support for sharing soundfont data between synthesizers (mkxp uses multiple synths), so if your memory usage is very high, you might want to try compiling fluidsynth from git master.
By default, mkxp switches into the directory where its binary is contained and then starts reading the configuration and resolving relative paths. In case this is undesired (eg. when the binary is to be installed to a system global, read-only location), it can be turned off by adding `-Dworkdir_current=true` to meson's build arguments.

View file

@ -69,7 +69,7 @@ RB_METHOD(httpPost) {
RB_UNUSED_PARAM;
VALUE path, postDataHash, rheaders;
rb_scan_args(argc, argv, "2", &path, &postDataHash, &rheaders);
rb_scan_args(argc, argv, "21", &path, &postDataHash, &rheaders);
SafeStringValue(path);
VALUE ret;
@ -100,7 +100,7 @@ RB_METHOD(httpPostBody) {
RB_UNUSED_PARAM;
VALUE path, body, ctype, rheaders;
rb_scan_args(argc, argv, "3", &path, &body, &ctype, &rheaders);
rb_scan_args(argc, argv, "31", &path, &body, &ctype, &rheaders);
SafeStringValue(path);
SafeStringValue(body);
SafeStringValue(ctype);