Hi Wolf, welcome to the mailing list. Great to hear you started working again on DOG. Putting it on Github (or some other publicly accessible repo) sounds like a good idea :)
Looking at https://gitlab.com/FreeDOS/util/dog, that seems to be version 0.83c. Is this the latest publicly available version? Otherwise we should update the package. > Now a question: > What are your dev setups like? I'm on a linux host computer and I've been > using both DOSBox and QEMU to build and test in. I find though that it's a > bit of a chore, since DOSBox crashes randomly (like when compiling), or QEMU > segfaults when I mount my dog source directory as a virtual FAT drive. So now > I'm looking at setting up Dosemu2 (I remember using doemu ~20 years ago). I mainly edit the source code of the DOS programs I work on with my Mac and compile them inside DosBox-X. For me, this is quite stable. I would like to test Dosemu2, but that seems not to be fully ported to Mac yet. I use OpenWatcom 1.9 to compile my programs under DOS(Box), but also have setup Github actions for some projects to automatically build my commits using a Linux container with OpenWatcom v2 and IA16-GCC. While somewhat experimental, the Linux port of OpenWatcom v2 and IA16-GCC work good enough to produce functional kernel and FDISK binaries. We did not encounter major issues in recent times. You might get some inspiration from the public repos under https://github.com/FDOS. Regarding the edit-build-test cycle, this is where DosBox comes to its limit. Programs that use the ordinary DOS API and some BIOS interrupts tend to run fine. But I had for example some minor problems with missing INT13 interrupt functions. Though the DosBox-X people were fast at implementing the missing pieces after I filed a report at their issue tracker. The kernel and other low-level stuff I test under 86box or on a real machine. Regarding debugging, for me the Watcom Debugger is a good enough debugger to debug most of the user space programs. It has a TUI and supports symbolic debugging. There are also free sophisticated debuggers like lDebug (command line based) that might be worth a look at, albeit I would consider this more geared towards assembly. So, once again welcome. Bernd _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
