You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+30-12Lines changed: 30 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,18 +122,33 @@ versions earlier than v1.13 because of language features added in that version
122
122
(binary literals).
123
123
124
124
The project uses the Go module system and dependencies will be resolved
125
-
automatically. Do note however, that you will required the SDL development
126
-
libraries for the Go SDL module to compile.
125
+
automatically. Do note however, that you will also require the SDL development
126
+
kit installed on the system. For users of UNIX like systems, installation from
127
+
your package manager is the easiest option (for MacOS use the homebrew package
128
+
manager https://formulae.brew.sh/formula/sdl2)
127
129
128
130
Compile with GNU Make
129
131
130
-
> make build
132
+
> make release
131
133
132
134
During development, programmers may find it more useful to use the go command
133
135
directly
134
136
135
137
> go run gopher2600.go
136
138
139
+
## Cross-Compilation
140
+
141
+
Native compilation of a Windows executable has not yet been tried. But
142
+
cross-compilation does work via the Makefile:
143
+
144
+
> make cross_windows
145
+
146
+
Or for a statically linked binary:
147
+
148
+
> make cross_windows_static
149
+
150
+
This has been tested on a Linux system with mingw installed.
151
+
137
152
## Basic usage
138
153
139
154
Once compiled run the executable with the help flag:
@@ -238,15 +253,16 @@ Help is available with the HELP command. Help on a specific topic is available
238
253
by specifying a keyword. The list below shows the currently defined keywords.
239
254
The rest of the section will give a brief run down of debugger features.
240
255
241
-
AUDIO BALL BREAK CARTRIDGE CLEAR
242
-
CONTROLLER CPU DISASSEMBLY DISPLAY DROP
243
-
GREP HALT HELP INSERT JOYSTICK
244
-
KEYPAD LAST LINT LIST MEMMAP
245
-
MISSILE ONHALT ONSTEP ONTRACE PANEL
246
-
PATCH PEEK PLAYER PLAYFIELD POKE
247
-
PREF QUANTUM QUIT RAM RESET
248
-
RUN SCRIPT STEP SYMBOL TIA
249
-
TIMER TRACE TRAP TV WATCH
256
+
[ $f000 SEI ] >> help
257
+
AUDIO BALL BREAK CARTRIDGE CLEAR
258
+
CONTROLLER CPU DISASSEMBLY DISPLAY DROP
259
+
GREP HALT HELP INSERT JOYSTICK
260
+
KEYPAD LAST LINT LIST LOG
261
+
MEMMAP MISSILE ONHALT ONSTEP ONTRACE
262
+
PANEL PATCH PEEK PLAYER PLAYFIELD
263
+
POKE PREF QUANTUM QUIT RAM
264
+
RESET RUN SCRIPT STEP SYMBOL
265
+
TIA
250
266
251
267
The debugger allows tab-completion in most situations. For example, pressing `W` followed by the Tab key on your keyboard, will autocomplete the `WATCH` command. This works for command arguments too. It does not currently work for filenames, or symbols. Given a choice of completions, the Tab key will cycle through the available options.
252
268
@@ -274,6 +290,8 @@ is `.config/gopher2600`.
274
290
275
291
For MacOS the directory for release executables is `~/Library/Application Support/gopher2600`
276
292
293
+
For Window, files will be in the user's `Application Data/gopher2600` folder
294
+
277
295
In all instances, the directory, sub-directory and files will be created automatically
0 commit comments