lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores)

RealNC

I uploaded a debug build as well:

https://github.com/realnc/dosbox-core/releases/download/latest_build/linux-armhf-dbg.zip

mitu

@RealNC I think it might be targeting the wrong (ARM) dynrec.

RealNC

@mitu said in lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores):

I think it might be targeting the wrong (ARM) dynrec.

It's the correct one for ARMv7. Does 32-bit stand-alone dosbox run fine when dynrec is enabled? (core = dynamic in the .conf file.) I think the rpi4 CPU is supposed to be backwards compatible with 32-bit ARMv7. So if stand-alone 32-bit dosbox with the same dynrec has the same issue, then this could be a bug in the dosbox dynrec.

I'll also put a 64-bit ARMv8 build up to see how that one behaves.

RealNC

Btw, if you disable the dynrec by setting the core's "System: CPU core" option to "normal", does it work then?

mitu

@RealNC Yes, the RPI4 (at least on Raspbian) should fall into the 32 bit ARMv7 category. Sadly 64 bit (ARMv8) would not work out-of-the-box since Raspbian has no 64 bit userspace support.

I tried the recommended settings (core and .conf) and it's still crashing - while the normal dosbox (upstream SVN) or dosbox-staging work fine.

RetroPie uses these build instructions when packaging upstream dosbox.

My testing .conf has just an autoexec section for starting Q1:

[autoexec]
mount c: /home/pi/roms/pc-data
c:
cd \quake1
quake -nocdaudio
exit

I think I'll try again to build the core - modifying the Makefile - and see if I can get it running locally, it might be an issue with the automated build.

RealNC

@mitu said in lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores):

I tried the recommended settings (core and .conf) and it's still crashing

Can you get a backtrace in this case? The old crash pointed to the dynrec, so with it disabled it should point somewhere else.

mitu

@RealNC Re-tested with core = dynamic and the crash is similar. Using the "System: CPU core" option to "normal" doesn't crash, but it's obviously slow.

RealNC

It's very difficult to debug this on my end, as I don't have any ARM devices. To check if this an issue with the toolchain, I built the regular dosbox-svn core with it:

http://83.212.109.87/~realnc/tmp/dosbox_svn_libretro.zip

Does it also crash?

mitu

@RealNC said in lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores):

Does it also crash?

No, it doesn't crash. I don't think the toolchain is at fault. Since the last update I managed to compile it natively (modifying the LDFLAGS) and I get a crash also.

I don't know if the core you linked (svn) is synchronized to the latest Dosbox SVN tag (I think dosbox-core is), but I'll install from source the latest Dosbox and see if maybe there's a recent regression.

RealNC

@mitu said in lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores):

I don't know if the core you linked (svn) is synchronized to the latest Dosbox SVN tag

No, it is kept in sync with SVN trunk. So that's not it.

I found something that might be the cause of it. I'll upload a new test build shortly.

RealNC

If you want to test locally if this is indeed the issue, edit Makefile.libretro and change this line near the beginning of the file:

CXXFLAGS += -std=c++17 -Dregister=

to:

CXXFLAGS += -std=c++17

Then do:

make <your other options here> targetclean`

and build again.

(targetclean only cleans core files, not deps, so that you don't have to rebuild deps again.)

mitu

@RealNC I'll give it a shot, thank you.

mitu

Well, it's not crashing anymore - this may be the winning ticket. If you have an automated build, I can give it a test.

RealNC

Well, that will teach me to assume that the register keyword is useless. I disabled it to get rid of the GCC warning about register being invalid in C++ now. Turns out that even if you specify an actual register to be used for a variable using __asm("register_name"), you still need the register keyword...

Oops.

Thanks for the help! I'll add the ARM build to the libretro buildbot and upload fixed builds soon.

RealNC

(I hope I'm not stealing too much of your time with all this :-P)

Automated build is now up:

https://github.com/realnc/dosbox-core/releases/download/latest_build/linux-armhf.zip

Now, the above is built with GCC on actual Ubuntu ARM. However, building it this way is extremely slow (takes like an hour to build) because I have to emulate ARM in QEMU inside the Azure VM github provides. So I'd like to cross-compile from Intel to ARM instead using Clang. And that build is here:

http://83.212.109.87/~realnc/tmp/linux-armhf-clang.zip

Can you check if the Clang build works just as well as the GCC one? (Assuming the GCC automated build works, that is.)

mitu

@RealNC said in lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores):

https://github.com/realnc/dosbox-core/releases/download/latest_build/linux-armhf.zip

This works, no crash.

Now, the above is built with GCC on actual Ubuntu ARM. However, building it this way is extremely slow (takes like an hour to build) because I have to emulate ARM in QEMU inside the Azure VM github provides. So I'd like to cross-compile from Intel to ARM instead using Clang. And that build is here:
http://83.212.109.87/~realnc/tmp/linux-armhf-clang.zip

This one doesn't work, it crashes - but strangely not if I run in through gdb.

RealNC

The 1 hour GCC build it will have to be then.

Thanks!

jul059

Not sure where to post this, but dosbox-staging might be worth considering as a core. The pixel-perfect scaling mode looks interesting.

RealNC

@jul059 said in lr-dosbox-svn / lr-dosbox-core (new dosbox libretro cores):

Not sure where to post this, but dosbox-staging might be worth considering as a core. The pixel-perfect scaling mode looks interesting.

Pixel-perfect scaling is done by the frontend in libretro cores. Usually called "integer scaling" (RetroArch calls it that, for example.) If you enable that in the frontend, and also turn off the "Video: Aspect ratio correction" core option, you get 100% pixel-perfect scaling. With aspect correction enabled, you get what is sometimes called "near-perfect" scaling.

nikitau

Hey, kinda new to this forum so idk if necrobumping is frowned upon, but wanted to share my recent experience with this. I actually got dosbox-core to work quite fine on a RPi4 without any modification of the binary build from github. The setup script is pretty basic and doesn't do much besides downloading the binary and installing it:

#!/usr/bin/env bash

# This file is part of The RetroPie Project
#
# The RetroPie Project is the legal property of its developers, whose names are
# too numerous to list here. Please refer to the COPYRIGHT.md file distributed with this source.
#
# See the LICENSE.md file at the top-level directory of this distribution and
# at https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/LICENSE.md
#

rp_module_id="lr-dosbox-core"
rp_module_desc="DOS emulator LIBRETRO"
rp_module_help="ROM Extensions: .bat .com .exe .sh\n\nCopy your DOS games to $ROMDIR/pc"
rp_module_licence="GPL2 https://raw.githubusercontent.com/libretro/dosbox-libretro/master/COPYING"
rp_module_section="exp"
rp_module_flags=""

function sources_lr-dosbox-core() {
    wget "https://github.com/realnc/dosbox-core/releases/download/latest_build/linux-armhf.zip"
}

function build_lr-dosbox-core() {
    unzip linux-armhf.zip
    md_ret_require="$md_build/dosbox_core_libretro.so"
}

function install_lr-dosbox-core() {
    md_ret_files=(
        'dosbox_core_libretro.so'
    )
}

function configure_lr-dosbox-core() {
    mkRomDir "pc"
    ensureSystemretroconfig "pc"

    addEmulator 0 "$md_id" "pc" "$md_inst/dosbox_core_libretro.so"
    addSystem "pc"
}

I only tested it on Prehistorik 2 and Wolfenstein 3D, but they seem to get decent performance. Control mapping and sound seem to work just fine, but I should test performance against vanilla dosbox and see if it holds for more demanding titles (eg. Blood or Duke Nukem).

Sidenote: I did have a lot of the dependencies installed beforehand and the binary does come bundled with some of them so idk at this moment if there is some prerequisite that should be installed by the script. Maybe fluidsynt and/or bassmidi(?)