mirror of
https://github.com/Interlisp/maiko.git
synced 2026-01-14 15:36:34 +00:00
80c9c796c5
* Update struct DevRec methods to take a "void *" parameter since they get called with different xxxInterface records depending on whether they are a keyboard, mouse, or display. Introduce GenericReturnVoid method implementation for use where needed with DevRec methods. (see mouseif.c) * Cast functions implementing DevRec methods as appropriate to match the method signature. * Update struct DspInterfaceRec methods cleardisplay, bitblt_to_screen, mouse_invisible, and mouse_visible to declare the parameters they require and all return unsigned long results (though it's not clear that this is actually the correct type). Requires updating dosmouse.c method implementations. * Update GenericReturnT and GenericPanic method implementations to have the signature required by the method slots they are used in. * Correct DOS-only section with incorrect arguments to device.exit call for the mouse. * Use include "dspifdefs.h" for prototypes for GenericReturnXXX method implementations.
Maiko
Maiko is the implementation of the Medley Interlisp virtual machine, for a byte-coded Lisp instruction set and some low-level functions for connecting with Lisp for access to display (via X11) and disk etc.
For an overview, see Medley Interlisp Introduction.
See the Medley repository for
- Issues (note that maiko issues are there too)
- Discussions (Q&A, announcements, etc)
- Medley's README
Bug reports, feature requests, fixes and improvements, support for additional platforms and hardware are all welcome.
Development Platforms
We are developing on FreeBSD, Linux, MacOS, and Solaris currently on arm7l, arm64, PowerPC, SPARC, i386, and x86_64 hardware.
Building Maiko
Building requires clang, make, X11 client libraries (libx11-dev). For example,
$ sudo apt update
$ sudo apt install clang make libx11-dev
$ cd maiko/bin
$ ./makeright x
- The build will (attempt to) detect the OS-type and cpu-type. It will build binaries
ldeandldexin../ostype.cputype(with .o files in..ostype.cputype-x. For example, Linux on a 64-bit x86 will uselinux.x86_64, while MacOS 11 on a (new M1) Mac will usedarwin.aarch64. - If you prefer using
gccoverclang, you will need to edit the makefile fragment for your configuration (makefile-ostype.cputype-x) and comment out the line (with a #) that definesCCforclangand uncomment the line (delete the #) for the line that definesCCforgcc. - There is a cmake configuration (TBD To Be Described here).
Building For MacOS
- Running on MacOS requires an X server, and building on a Mac requires X client libraries. An X-server for MacOS (and X11 client libraries) can be freely obtained at https://www.xquartz.org/releases
Building for Windows 10
Windows 10 currently requires "Docker for Desktop" or WSL2 and a (Windows X-server). See Medley's README for more.