Looking at winsock2.h it appears some POSIX'ish methods are available for sockets, so it may not be hard to support
MingWin?
.
RTEMS Tools Project - Source Builder Error Report
Build: error: building s2xwm1
x86_64-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -DFAST_UART -O2 -g -pipe -I/c/msys64/home/mayes/dev/rtems/rsb/rtems/build/tmp/sb-mayes/5s/c/msys64/home/mayes/dev/rtems/5/include -MT func.o -MD -MP -MF .deps/func.Tpo -c -o func.o func.c
func.c:26:10: fatal error: sys/socket.h: No such file or directory
26 | #include <sys/socket.h>
make
[1]
:
* [Makefile:380: func.o] Error 1
make
[1]
:
* Waiting for unfinished jobs....
mv -f .deps/leon3.Tpo .deps/leon3.Po
make
[1]
: Leaving directory '/c/msys64/home/mayes/dev/rtems/rsb/rtems/build/s2xwm1/sis-2.18'
make:
* [Makefile:260: all] Error 2
shell cmd failed: sh -ex /c/msys64/home/mayes/dev/rtems/rsb/rtems/build/s2xwm1/do-build
error: building s2xwm1
I can make sis compile under mingw but only without the gdb interface. The windows socket API is slightly different from unix, and I am not a windows user...
I can see two short-term fixes: disable the gdb interface in sis when building for mingw (WIN32) or disable building sis altogether when building RSB on a WIN32 host.
note: if you are on windows 10, you could always install WSL with an ubuntu 18.04 image and build RSB there ...
I was thinking about native Windows winsock calls so I am not sure if this makes a difference. Is there an issue I am not aware of?
It is not so much winsock, but terminal handling. Windows and mingw/msys does not support termios, thus no readline or linenoise. And reverting to fgets() feels a bit primitive. However, the newer mingw-w64/msys2 has a port of readline which is also used by gdb et al. So going with msys2 would make the porting easier as only the winsock needs to be addressed ...
-
Improve gdb watchpoint handling/reporting
-
Support building on Mingw-W64
-
Stop flushing sparc reg windows on gdb break
-
updates
#3816
