Emulators - Revision history

Aoineko at 23:37, 3 February 2025

2025-02-03T23:37:47Z

2024-10-16T14:38:53Z

‎How to debug using VS Code

2024-01-05T00:00:06Z

‎How to debug using VS Code

2023-07-26T10:22:00Z

‎How to debug using VS Code

2023-07-25T11:11:11Z

‎How to debug using VS Code

2023-07-25T11:10:37Z

‎How to debug using VS Code

2023-07-23T23:34:43Z

‎How to debug using VS Code

2023-07-23T23:32:44Z

‎How to debug using VS Code

2023-07-23T23:28:32Z

‎{{openMSX}} openMSX

2023-07-23T23:28:05Z

‎{{Emulicious}} Emulicious

@@ Line 1: / Line 1: @@
 == Support ==
 MSXgl's [[Build tool]] can automatically launch the emulator of your choice with a configuration that match your project options. Not all emulators support all available options.
@@ Line 6: / Line 7: @@
 <html><iframe
      width="100%"
-     height="430px"
+     height="450px"
      title="Emulator support"
      src="https://docs.google.com/spreadsheets/d/e/2PACX-1vQ_k1n0StRUX8zagkpZrF-ZtkFYwanLKVA6wUm2jlcjMFjCr44wIb6aEKDQcAD7wn0XLwRjYNL7Lk_e/pubhtml">

@@ Line 46: / Line 46: @@
 ==== How to debug using VS Code ====
-Here are the steps for debugging your program with Emulicious from VS Code:
+Here are the steps for debugging your program with Emulicious from [[VS Code]]:
 . Install [https://marketplace.visualstudio.com/items?itemName=emulicious.emulicious-debugger Emulicious VS Code extension].

@@ Line 53: / Line 53: @@
 . Create a <tt>launch.json</tt> from the "Run and Debug" panel. Configuration section should look like:
-<pre>
+<syntaxhighlight lang="json">
 "configurations": [
+         {
@@ Line 70: / Line 70: @@
+         }
+     ]
-</pre>
+</syntaxhighlight>
 Replace <tt>${command:AskForProgramName}</tt> by <tt>emul/rom/mygame.rom</tt> (where "mygame" is your own game name).
 If you already have a <tt>launch.json</tt>, select the "Add configuration" option and select one of the 2 Emulicious configuration.

@@ Line 52: / Line 52: @@
 . Setup "Emulicious Path" in Emulicious extension's settings.
-. Create a <tt>launch.json</tt> from the "Run and Debug" panel. Configuration should look like:
+. Create a <tt>launch.json</tt> from the "Run and Debug" panel. Configuration section should look like:
 <pre>
 "configurations": [

@@ Line 77: / Line 77: @@
 . Now you are ready to debug your application from VS Code. Go to "Run and Debug" panel and select Attach (to attach to a currently running game on Emulicious) or Launch (to launch your game in Emulicious). If "stopOnEntry" is set to true in your <tt>launch.json</tt>, the VS Code debugger should break at the beginning of your <tt>main()</tt> function.
 You can found more information about the VS Code debugger on Internet. For example: https://code.visualstudio.com/docs/editor/debugging
 === {{bleuMSX}} blueMSX ===

← Older revision		Revision as of 11:10, 25 July 2023
Line 79:		Line 79:

	You can found more information about the VS Code debugger on Internet. For example: https://code.visualstudio.com/docs/editor/debugging		You can found more information about the VS Code debugger on Internet. For example: https://code.visualstudio.com/docs/editor/debugging
		+
		+	<img style="width:50%;" src="https://raw.githubusercontent.com/aoineko-fr/MSXgl/main/engine/doc/img/tools/emulicious_2.jpg" />

	=== {{bleuMSX}} blueMSX ===		=== {{bleuMSX}} blueMSX ===

← Older revision		Revision as of 23:32, 23 July 2023
Line 77:		Line 77:

	5. Now you are ready to debug your application from VS Code. Go to "Run and Debug" panel and select Attach (to attach to a currently running game on Emulicious) or Launch (to launch your game in Emulicious). If "stopOnEntry" is set to true in your <tt>launch.json</tt>, the VS Code debugger should break at the beginning of your <tt>main()</tt> function.		5. Now you are ready to debug your application from VS Code. Go to "Run and Debug" panel and select Attach (to attach to a currently running game on Emulicious) or Launch (to launch your game in Emulicious). If "stopOnEntry" is set to true in your <tt>launch.json</tt>, the VS Code debugger should break at the beginning of your <tt>main()</tt> function.
		+
		+	You can found more information about the VS Code debugger on Internet. For example, those tutorials: https://code.visualstudio.com/docs/introvideos/basics

	=== {{bleuMSX}} blueMSX ===		=== {{bleuMSX}} blueMSX ===

@@ Line 14: / Line 14: @@
 === {{openMSX}} openMSX ===
-To enable MSX turbo R, FM-PAC or OPL4 emulation, you need to get proprietary system ROMs not included in openMSX for copyright reason. You can find them on the Internet ([http://www.msxarchive.nl/pub/msx/emulator/openMSX/systemroms.zip here] or [https://download.file-hunter.com/System%20ROMs/Full%20Set%20System%20ROM's%20(OpenMSX)%20-%2022-03-2022.zip here] for example).
+To enable MSX turbo R, FM-PAC or OPL4 emulation, you need to get proprietary system ROMs not included in [https://openmsx.org/ openMSX] for copyright reason. You can find them on the Internet ([http://www.msxarchive.nl/pub/msx/emulator/openMSX/systemroms.zip here] or [https://download.file-hunter.com/System%20ROMs/Full%20Set%20System%20ROM's%20(OpenMSX)%20-%2022-03-2022.zip here] for example).
 You also need those system ROMs to launch MSX-DOS or BASIC binaries application from a disk. Once you have installed the system ROMs, you need to select a machine that contains a disk: for example the Philips VG-8235 (PAL) or Sony HB-F1XD (NTSC). Set the machine as the default one in openMSX and set <tt>EmulMachine</tt> to false in your project configuration (to prevent the Build tool to reset the machine a launch).

@@ Line 21: / Line 21: @@
 === {{Emulicious}} Emulicious ===
-Here is some tips to test your MSXgl program using Emulicious.
+Here is some tips to test your MSXgl program using [https://emulicious.net/ Emulicious].
 ==== How to run a MSX-DOS or BASIC program ====