2017-09-18 07:58:47 +00:00
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE - RUN doctoc TO UPDATE -->
2017-09-18 08:02:33 +00:00
2017-09-18 07:58:47 +00:00
- [Visual Boy Advance - M ](#visual-boy-advance---m )
- [Building ](#building )
2019-08-20 07:31:38 +00:00
- [Building a Libretro core ](#building-a-libretro-core )
- [Visual Studio Support ](#visual-studio-support )
- [Dependencies ](#dependencies )
2017-09-18 07:58:47 +00:00
- [Cross compiling for 32 bit on a 64 bit host ](#cross-compiling-for-32-bit-on-a-64-bit-host )
- [Cross Compiling for Win32 ](#cross-compiling-for-win32 )
- [CMake Options ](#cmake-options )
- [MSys2 Notes ](#msys2-notes )
- [Debug Messages ](#debug-messages )
- [Reporting Crash Bugs ](#reporting-crash-bugs )
- [Contributing ](#contributing )
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
2017-08-14 20:56:54 +00:00
[![Join the chat at https://gitter.im/visualboyadvance-m/Lobby ](https://badges.gitter.im/visualboyadvance-m/Lobby.svg )](https://gitter.im/visualboyadvance-m/Lobby)
2019-08-20 07:31:38 +00:00
[![travis ](https://travis-ci.org/visualboyadvance-m/visualboyadvance-m.svg?branch=master )](https://travis-ci.org/visualboyadvance-m/visualboyadvance-m)
[![appveyor ](https://ci.appveyor.com/api/projects/status/5ckx25vct1q1ovfc?svg=true )](https://ci.appveyor.com/project/ZachBacon65337/visualboyadvance-m-2ys5r)
2018-06-27 02:15:22 +00:00
2016-12-23 13:38:50 +00:00
# Visual Boy Advance - M
Game Boy Advance Emulator
2019-08-20 07:31:38 +00:00
The Forum is here: https://vba-m.com/forums/
2016-12-23 13:38:50 +00:00
2017-03-06 10:03:15 +00:00
Windows and Mac builds are in the [releases tab ](https://github.com/visualboyadvance-m/visualboyadvance-m/releases ).
2019-03-03 01:34:36 +00:00
Your distribution may have packages available as well, search for "vbam" or "visualboyadvance-m".
2017-03-06 10:03:15 +00:00
2017-03-06 10:10:06 +00:00
It is also generally very easy to build from source, see below.
2019-03-03 01:34:36 +00:00
If you are using the windows binary release and you need localization, unzip
the `translations.zip` to the same directory as the executable.
2019-08-31 16:23:34 +00:00
If you are having issues, try resetting the config file first, go to `Help -> Factory Reset` .
2018-06-23 20:45:35 +00:00
2016-12-23 13:38:50 +00:00
## Building
The basic formula to build vba-m is:
2017-08-14 20:56:54 +00:00
```shell
2016-12-23 13:38:50 +00:00
cd ~ & & mkdir src & & cd src
git clone https://github.com/visualboyadvance-m/visualboyadvance-m.git
cd visualboyadvance-m
./installdeps
# ./installdeps will give you build instructions, which will be similar to:
mkdir build & & cd build
cmake ..
2017-08-14 20:56:54 +00:00
make -j`nproc`
2016-12-23 13:38:50 +00:00
```
2019-03-28 21:45:06 +00:00
`./installdeps` is supported on MSys2, Linux (Debian/Ubuntu, Fedora, Arch,
2019-08-20 07:31:38 +00:00
Solus, OpenSUSE, Gentoo and RHEL/CentOS) and Mac OS X (homebrew, macports or
fink.)
2016-12-23 13:38:50 +00:00
2019-12-07 16:58:12 +00:00
The Ninja cmake generator is also now supported.
auto deps for visual studio, take 1
Use vcpkg to build deps when Visual Studio on Windows is detected, this
only happens on first build, but does take a while because things like
wxWidgets need to be built. Building from the developer command line is
also supported.
I considered making a pre-built tarball available, but the resulting
files are just too big for this to be practical.
Make the necessary cmake code changes for this to work and to use the
vcpkg packages, which work just like on linux or have other cmake glue
code available.
To do this, we make vcpkg a submodule, use git to checkout all
submodules, then just build and use the `vcpkg.exe`. Then we set the
CMAKE_TOOLCHAIN_FILE to the vcpkg toolchain and also include it
directly, why this is necessary I don't know, without it it doesn't work
in the IDE but does on the command line.
All of this requires no vcpkg integration with either the user or the
project. A user-wide `ENV{VCPKG_ROOT}` is also supported.
Fix the dynamic arrays in the GBA core, MSVC follows the C++ standard on
this and gcc does not.
TODO: add the necessary gcc flags to make this an error in cmake.
Use `wxArrayString` instead of `std::vector<wxString>` in
`src/wx/strutils.cpp` which is used in options parsing. This was
necessary because of a bizarre linker error with wxWidgets when using
Visual Studio:
https://trac.wxwidgets.org/ticket/10884#comment:46
In `src/wx/panel.cpp` make sure the unimplemented D3D renderer code does
not get compiled if it's actually `OFF`.
Also fix the new spacer code for the drawing panel to not combine
`wxEXPAND` with `wxALIGN_CENTER`, which is an error on wxWidgets 3.1.2,
which is what vcpkg uses. The drawing panel seems to be automatically
stretched to the max size automatically anyway.
TODO: if all of this works, we'll need an Appveyor set up for visual
studio.
Signed-off-by: Rafael Kitover <rkitover@gmail.com>
2019-03-21 23:01:46 +00:00
2019-07-23 11:24:59 +00:00
## Building a Libretro core
```
Clone this repo and then,
$ cd src
$ cd libretro
$ make
Copy vbam_libretro.so to your RetroArch cores directory.
```
2019-08-20 07:31:38 +00:00
## Visual Studio Support
auto deps for visual studio, take 1
Use vcpkg to build deps when Visual Studio on Windows is detected, this
only happens on first build, but does take a while because things like
wxWidgets need to be built. Building from the developer command line is
also supported.
I considered making a pre-built tarball available, but the resulting
files are just too big for this to be practical.
Make the necessary cmake code changes for this to work and to use the
vcpkg packages, which work just like on linux or have other cmake glue
code available.
To do this, we make vcpkg a submodule, use git to checkout all
submodules, then just build and use the `vcpkg.exe`. Then we set the
CMAKE_TOOLCHAIN_FILE to the vcpkg toolchain and also include it
directly, why this is necessary I don't know, without it it doesn't work
in the IDE but does on the command line.
All of this requires no vcpkg integration with either the user or the
project. A user-wide `ENV{VCPKG_ROOT}` is also supported.
Fix the dynamic arrays in the GBA core, MSVC follows the C++ standard on
this and gcc does not.
TODO: add the necessary gcc flags to make this an error in cmake.
Use `wxArrayString` instead of `std::vector<wxString>` in
`src/wx/strutils.cpp` which is used in options parsing. This was
necessary because of a bizarre linker error with wxWidgets when using
Visual Studio:
https://trac.wxwidgets.org/ticket/10884#comment:46
In `src/wx/panel.cpp` make sure the unimplemented D3D renderer code does
not get compiled if it's actually `OFF`.
Also fix the new spacer code for the drawing panel to not combine
`wxEXPAND` with `wxALIGN_CENTER`, which is an error on wxWidgets 3.1.2,
which is what vcpkg uses. The drawing panel seems to be automatically
stretched to the max size automatically anyway.
TODO: if all of this works, we'll need an Appveyor set up for visual
studio.
Signed-off-by: Rafael Kitover <rkitover@gmail.com>
2019-03-21 23:01:46 +00:00
For visual studio, dependency management is handled automatically with vcpkg,
just clone the repository with git and build with cmake. You can do this from
the developer command line as well. 2019 will not work yet for building
dependencies, but you can build the dependencies in 2017 and then use the
project from 2019.
Using your own user-wide installation of vcpkg is supported, just make sure the
environment variable `VCPKG_ROOT` is set.
2019-07-03 23:28:48 +00:00
To build in the visual studio command prompt, use something like this:
```
2019-09-12 03:12:15 +00:00
mkdir build
cd build
2019-12-07 16:58:12 +00:00
cmake .. -DVCPKG_TARGET_TRIPLET=x64-windows -DCMAKE_BUILD_TYPE=Release -G Ninja
ninja
2019-07-03 23:28:48 +00:00
```
2019-08-20 07:31:38 +00:00
This support is new and we are still working out some issues, including support
for static builds.
## Dependencies
2017-02-11 22:18:38 +00:00
2016-12-23 13:38:50 +00:00
If your OS is not supported, you will need the following:
2017-08-14 20:56:54 +00:00
- C++ compiler and binutils
- [make ](https://en.wikipedia.org/wiki/Make_(software ))
- [CMake ](https://cmake.org/ )
- [git ](https://git-scm.com/ )
2019-08-20 07:31:38 +00:00
- [nasm ](https://www.nasm.us/ ) (optional, for 32 bit builds)
2016-12-23 13:38:50 +00:00
And the following development libraries:
2017-08-14 20:56:54 +00:00
- [zlib ](https://zlib.net/ ) (required)
- [mesa ](https://mesa3d.org/ ) (if using X11 or any OpenGL otherwise)
2019-09-01 20:37:39 +00:00
- [ffmpeg ](https://ffmpeg.org/ ) (optional, at least version `4.0.4` , for game recording)
2019-08-20 07:31:38 +00:00
- [gettext ](https://www.gnu.org/software/gettext/ ) and gettext-tools (optional, with ENABLE_NLS)
- [libpng ](http://www.libpng.org/pub/png/libpng.html ) (required)
- [SDL2 ](https://www.libsdl.org/ ) (required)
2017-08-14 20:56:54 +00:00
- [SFML ](https://www.sfml-dev.org/ ) (optional, for link)
2019-08-20 07:31:38 +00:00
- [OpenAL ](https://www.openal.org/ ) or [openal-soft ](https://kcat.strangesoft.net/openal.html ) (optional, a sound interface)
- [wxWidgets ](https://wxwidgets.org/ ) (required for GUI, 2.8 is still supported, --enable-stl is supported)
2016-12-23 13:38:50 +00:00
2017-02-20 21:20:09 +00:00
On Linux and similar, you also need the version of GTK your wxWidgets is linked
2019-08-20 07:31:38 +00:00
to (usually 2 or 3) and the xorg development libraries.
2017-02-20 21:20:09 +00:00
2016-12-23 13:38:50 +00:00
Support for more OSes/distributions for `./installdeps` is planned.
2017-03-23 21:09:17 +00:00
## Cross compiling for 32 bit on a 64 bit host
`./installdeps m32` will set things up to build a 32 bit binary.
This is supported on Fedora, Arch, Solus and MSYS2.
2016-12-23 13:38:50 +00:00
## Cross Compiling for Win32
`./installdeps` takes one optional parameter for cross-compiling target, which
may be `win32` which is an alias for `mingw-w64-i686` to target 32 bit Windows,
or `mingw-gw64-x86_64` for 64 bit Windows targets.
The target is implicit on MSys2 depending on which MINGW shell you started (the
2019-08-20 07:31:38 +00:00
value of `$MSYSTEM` .)
2016-12-23 13:38:50 +00:00
2019-08-20 07:31:38 +00:00
On Debian/Ubuntu this uses the MXE apt repository and works quite well.
2016-12-23 13:38:50 +00:00
2017-01-25 18:53:05 +00:00
On Fedora it can build using the Fedora MinGW packages, albeit with wx 2.8, no
OpenGL support, and no Link support for lack of SFML.
2016-12-23 13:38:50 +00:00
On Arch it currently doesn't work at all because the AUR stuff is completely
broken, I will at some point redo the arch stuff to use MXE as well.
## CMake Options
The CMake code tries to guess reasonable defaults for options, but you can
2019-08-20 07:31:38 +00:00
override them, for example:
2016-12-23 13:38:50 +00:00
2017-08-14 20:56:54 +00:00
```shell
2016-12-23 13:38:50 +00:00
cmake .. -DENABLE_LINK=NO
```
2016-12-23 14:10:54 +00:00
Of particular interest is making **RELEASE** or **DEBUG** builds, the default
mode is **RELEASE** , to make a **DEBUG** build use something like:
2017-08-14 20:56:54 +00:00
```shell
2016-12-23 14:10:54 +00:00
cmake .. -DCMAKE_BUILD_TYPE=Debug
```
2016-12-23 13:38:50 +00:00
Here is the complete list:
2017-10-22 22:35:56 +00:00
| **CMake Option** | **What it Does** | **Defaults** |
|-----------------------|----------------------------------------------------------------------|-----------------------|
| ENABLE_SDL | Build the SDL port | OFF |
| ENABLE_WX | Build the wxWidgets port | ON |
| ENABLE_DEBUGGER | Enable the debugger | ON |
| ENABLE_NLS | Enable translations | ON |
| ENABLE_ASM_CORE | Enable x86 ASM CPU cores (**BUGGY AND DANGEROUS**) | OFF |
| ENABLE_ASM | Enable the following two ASM options | ON for 32 bit builds |
| ENABLE_ASM_SCALERS | Enable x86 ASM graphic filters | ON for 32 bit builds |
| ENABLE_MMX | Enable MMX | ON for 32 bit builds |
2019-08-20 08:21:38 +00:00
| ENABLE_LINK | Enable GBA linking functionality (requires SFML) | AUTO |
2017-10-22 22:35:56 +00:00
| ENABLE_LIRC | Enable LIRC support | OFF |
2019-08-20 08:21:38 +00:00
| ENABLE_FFMPEG | Enable ffmpeg A/V recording | AUTO |
2019-07-10 23:47:16 +00:00
| ENABLE_ONLINEUPDATES | Enable online update checks | ON |
2017-10-22 22:35:56 +00:00
| ENABLE_LTO | Compile with Link Time Optimization (gcc and clang only) | ON for release build |
| ENABLE_GBA_LOGGING | Enable extended GBA logging | ON |
| ENABLE_DIRECT3D | Direct3D rendering for wxWidgets (Windows, **NOT IMPLEMENTED!!!** ) | ON |
| ENABLE_XAUDIO2 | Enable xaudio2 sound output for wxWidgets (Windows only) | ON |
2019-08-20 08:21:38 +00:00
| ENABLE_OPENAL | Enable OpenAL for the wxWidgets port | AUTO |
2018-08-10 23:35:49 +00:00
| ENABLE_SSP | Enable gcc stack protector support (gcc only) | OFF |
2019-01-02 16:23:26 +00:00
| ENABLE_ASAN | Enable libasan sanitizers (by default address, only in debug mode) | OFF |
2018-02-24 19:39:29 +00:00
| VBAM_STATIC | Try link all libs statically (the following are set to ON if ON) | OFF |
| SDL2_STATIC | Try to link static SDL2 libraries | OFF |
| SFML_STATIC_LIBRARIES | Try to link static SFML libraries | OFF |
| FFMPEG_STATIC | Try to link static ffmpeg libraries | OFF |
| SSP_STATIC | Try to link static gcc stack protector library (gcc only) | OFF except Win32 |
| OPENAL_STATIC | Try to link static OpenAL libraries | OFF |
2018-08-10 23:35:49 +00:00
| SSP_STATIC | Link gcc stack protecter libssp statically (gcc, with ENABLE_SSP) | OFF |
2017-05-24 11:25:45 +00:00
Note for distro packagers, we use the CMake module
[GNUInstallDirs ](https://cmake.org/cmake/help/v2.8.12/cmake.html#module:GNUInstallDirs )
to configure installation directories.
2016-12-23 13:38:50 +00:00
## MSys2 Notes
To run the resulting binary, you can simply type:
2017-08-14 20:56:54 +00:00
```shell
2016-12-23 13:38:50 +00:00
./visualboyadvance-m
```
in the shell where you built it.
2017-01-25 18:53:05 +00:00
If you built with `-DCMAKE_BUILD_TYPE=Debug` , you will get a console app and
will see debug messages, even in mintty.
2016-12-23 14:10:54 +00:00
2016-12-23 13:38:50 +00:00
If you want to start the binary from e.g. a shortcut or Explorer, you will need
2016-12-23 15:15:47 +00:00
to put `c:\msys64\mingw32\bin` for 32 bit builds and `c:\msys64\mingw64\bin`
for 64 bit builds in your PATH (to edit system PATH, go to Control Panel ->
System -> Advanced system settings -> Environment Variables.)
2016-12-23 13:38:50 +00:00
If you want to package the binary, you will need to include the MinGW DLLs it
depends on, they can install to the same directory as the binary.
For our own builds, we use MXE to make static builds.
2017-01-25 18:53:05 +00:00
## Debug Messages
We have an override for `wxLogDebug()` to make it work even in non-debug builds
of wx and on windows, even in mintty. Using this function for console debug
messages is recommended.
2017-09-18 07:58:47 +00:00
It works like `printf()` , e.g.:
2017-01-25 18:53:05 +00:00
```cpp
int foo = 42;
wxLogDebug(wxT("the value of foo = %d"), foo);
```
2017-09-18 07:58:47 +00:00
## Reporting Crash Bugs
2017-08-17 21:25:27 +00:00
If the emulator crashes and you wish to report the bug, a backtrace made with
debug symbols would be immensely helpful.
To generate one (on Linux and MSYS2) first build in debug mode by invoking
`cmake` as:
```shell
cmake .. -DCMAKE_BUILD_TYPE=Debug
```
After you've reproduced the crash, you need the core dump file, you may need to
do something such as:
```shell
ulimit -c unlimited
```
in your shell to enable coredump files.
[This
post](https://ask.fedoraproject.org/en/question/98776/where-is-core-dump-located/?answer=98779#post-id-98779)
explains how to retrieve core dump on Fedora Linux (and possibly other
distributions.)
Once you have the core dump file, open it with `gdb` , for example:
```shell
gdb -c core ./visualboyadvance-m
```
In the `gdb` shell, to print the backtrace, type:
```
bt
```
This may be a bit of a hassle, but it helps us out immensely.
2017-09-18 07:58:47 +00:00
## Contributing
2016-12-23 13:38:50 +00:00
2017-08-14 20:56:54 +00:00
Please keep in mind that this app needs to run on Windows, Linux and macOS at
2016-12-23 13:38:50 +00:00
the very least, so code should be portable and/or use the appropriate `#ifdef` s
and the like when needed.
Please try to craft a good commit message, this post by the great tpope explains
how to do so:
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
If you have multiple small commits for a change, please try to use `git rebase
-i` (interactive rebase) to squash them into one or a few logical commits (with
good commit messages!) See:
https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History if you are new to
this.