mupen64plus-core | Core module of the Mupen64Plus project

by mupen64plus C Version: nightly-build License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | mupen64plus-core Summary

mupen64plus-core is a C library typically used in Simulation applications. mupen64plus-core has no bugs, it has no vulnerabilities and it has medium support. You can download it from GitHub.

More documentation can be found on the Mupen64Plus website and you can find a more complete README file on the wiki. Mupen64Plus is based off of mupen64, originally created by Hacktarux. This package contains only the Mupen64Plus core library. For a fully functional emulator, the user must also install graphics, sound, input, and RSP plugins, as well as a user interface program (called a front-end).

Support

Quality

Security

License

Reuse

Support

mupen64plus-core has a medium active ecosystem.

It has 1080 star(s) with 211 fork(s). There are 75 watchers for this library.

It had no major release in the last 12 months.

There are 162 open issues and 292 have been closed. On average issues are closed in 275 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of mupen64plus-core is nightly-build

Quality

mupen64plus-core has 0 bugs and 0 code smells.

Security

mupen64plus-core has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

mupen64plus-core code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

mupen64plus-core does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

mupen64plus-core releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 596 lines of code, 18 functions and 2 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of mupen64plus-core

Get all kandi verified functions for this library.

mupen64plus-core Key Features

No Key Features are available at this moment for mupen64plus-core.

mupen64plus-core Examples and Code Snippets

No Code Snippets are available at this moment for mupen64plus-core.

Community Discussions

Trending Discussions on mupen64plus-core

Populate C# struct using Mupen64Plus Unmanaged C dll API command

QUESTION

Populate C# struct using Mupen64Plus Unmanaged C dll API command

Asked 2019-Aug-22 at 07:14

I'm using Mupen64Plus and the included m64p_test_rom.v64 file.

I'm using C# to talk to the mupen64plus.dll API which is written in C.

Problem

I'm trying to use its API command M64CMD_ROM_GET_HEADER to get the ROM Header from m64p_test_rom.v64, which contains properties like Name, Manufacturer ID, Country code. It looks like the command stores the data in a struct.

The problem is that when the API command is called to populate the struct, the variables remain null, it does not populate it with new values.

API

I'm using this C# API code from BizHawk to talk to mupen64plus.dll.

Commands

Mupen64Plus v2.0 Core Front-End Wiki

CoreDoCommand(m64p_command Command, int ParamInt, void *ParamPtr)

Command Enumerated type specifying which command should be executed.

ParamInt: An integer value which may be used as an input to the command.
ParamPtr: A pointer which may be used as an input to the command.
M64CMD_ROM_GET_HEADER

This will retrieve the header data of the currently open ROM. A ROM image must be open.

ParamInt: Pointer to a rom_header struct to receive the data.
ParamPtr: The size in bytes of the rom_header struct.

ROM Header struct

In my C# project I created a new struct to match the one in the Mupen64Plus's C source code. I'm not sure if I have converted it from C to C# correctly.

Mupen64Plus C m64p_types.h

...

ANSWER

Answered 2019-Aug-22 at 07:14

You have defined/passed the parameters to the method in the wrong order. The second parameter of the delegate is of type int and the third parameter is a void pointer in C and should be used to pass data as a reference. For example, you can find the following code in the link you sent (BizHawk/mupen64pluseCoreApi.cs) :

Source https://stackoverflow.com/questions/57603448

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install mupen64plus-core

To install the binary distribution of Mupen64Plus, su to root and run the provided install.sh script:. The install script will copy the executable to /usr/local/bin and a directory called /usr/local/share/mupen64plus will be created to hold plugins and other files used by mupen64plus. NOTE: By default, install.sh uses /usr/local for the install prefix. Although the user can specify an alternate prefix to install.sh at the commandline, the mupen64plus binary was compiled to look for the install directory in /usr/local, so specifying an alternate prefix to install.sh will cause problems (the mupen64plus front-end application will not find the directory containing the core library) unless the directory to which you install it is known by your dynamic library loader (ie, included in /etc/ld.conf.so) If you want to use a prefix other than /usr/local, you may also download the source code package and build with the PREFIX option (see below). After building mupen64plus and all plugins, su to root and type make install to install Mupen64Plus. The install process will copy the executable to $PREFIX/bin and a directory called $PREFIX/share/mupen64plus will be created to hold plugins and other files used by mupen64plus. By default, PREFIX is set to /usr/local. This can be changed by passing the PREFIX option to make.
directory specified on command line with --installdir
same directory as the mupen64plus binary
/usr/local/share/mupen64plus
/usr/share/mupen64plus
current working directory

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: