Open ramboza opened 2 years ago
I think modem support requires SDL_net or SDL2_net and I suspect your build was generated without?
Rderooy, thanks for hint !
Here is quick solution for MacOS and SDL2:
Inside of vs/sdlnet folder has saved SDL_net v1.x and extra script build-dosbox.sh to build it. The same story for SDL2_net...
After line 20: ... echo Compiling our internal SDL 2.x (cd vs/sdl2 && ./build-dosbox.sh) || exit 1
# prefer to compile against our own copy of SDLnet 1.x
echo Compiling our internal SDLnet 2.x
(cd vs/sdl2net && ./build-dosbox.sh) || exit
new="-I$top/vs/sdl2net/linux-host/include/SDL2 "
nld="-L$top/vs/sdl2net/linux-host/lib "
export CFLAGS="$new$CFLAGS -g3"
export LDFLAGS="$nld$LDFLAGS -g3"
export CPPFLAGS="$new$CPPFLAGS -g3"
export CXXFLAGS="$new$CXXFLAGS -g3"
In the end run build script and enjoy serial functionality again ! ;)
P.S. Can I do PR with this fix ?
Sure, create a PR and submit it. But I am not the approver ;-)
Describe the bug
Serial port configurations regarding nullmodem or modem is not working on macOS version
Steps to reproduce the behaviour
To reproduce issue try to use
serial1 = modem or serial1 = nullmodem
parameters for any serialX port inside of [serial] configuration
Expected behavior
No response
What operating system(s) this bug have occurred on?
MacOS Monterey v12.4
What version(s) of DOSBox-X have this bug?
Dosbox-x: 0.83.25
Used configuration
Output log
Additional information
No response
Have you checked that no similar bug report(s) exist?
Code of Conduct & Contributing Guidelines