PATH="$PWD/bin:$PWD/var/out:$PATH" EXHIBIT_INTERACT=interact-x11. Now getting a bit further, but stuck at LINK interact-x11 How about AMS_BIN, AMS_LIB, and AMS_MNT as environment variables to set these locations? These categories (tools, modules, and server-provided) correspond the the bin, lib, and mnt subdirectories of ams-68k-bin.
#Executor mac emulator ubuntu code
Disk images are mounted by emulated system code and therefore use the same mechanism. fonts, cursors, and icons), and its own code. This is how an application accesses any data files it uses, system resources (e.g. Instead, it makes requests of a file server to which it's connected over a socket. These are all loaded directly by xv68k and can be located anywhere that ams.vx can find them.Īnything else is loaded by emulated code, which is not given direct access to the native file system. It also loads modules, which modify the run-time environment in various ways. The main program it runs is app (which launches a Mac application). Xv68k works like a language interpreter, except its programs are 68K machine code. Native programs and scripts can be assumed to be found in PATH, but emulated code needs its own solution. In any case, the ams.vx launcher script needs to know where to find things. I see value in both self-contained application packages and a general emulator package with applications kept separately. To be honest, I'm not entirely sure where they should all go and I'd welcome the guidance of someone more knowledgeable.
#Executor mac emulator ubuntu plus
You'll need half a dozen plus native binaries, as well as the emulated ams-foo modules, app tool, and any 68K Mac applications - in addition to the ams launcher script, which must be modified to find everything else (since it currently expects to be run out of the repository). I haven't tried to walk anyone through this before. On the other hand, you're treading new ground - not merely compiling the emulator, but packaging it. On the one hand, things are very simple - apt-install a few packages, clone, cd, and run make ams-x11. I admit it's not perfect, but I'm open to making improvements (e.g. The HOWTO is geared toward users who don't necessarily have experience building projects from source and tries to make it as simple as possible, at the cost of taking some shortcuts. A front end for X11 users is provided by the interact-x11 program, which is built by the ams-x11 target. A front end, which displays the screen and relays input events, is required for interactive use (and has no knowledge of Mac emulation, per se). The emulator itself is platform-independent, relying only on POSIX. The first command executed by the ams-x11 target's recipe builds vx already - an additional command to do so is redundant.
0 kommentar(er)
