Difference between revisions of "Testing library samples"
From MSX Game Library
(→Samples) |
|||
| Line 3: | Line 3: | ||
{| | {| | ||
|- | |- | ||
| − | | | + | |<tt>📁 projects</tt> || |
|- | |- | ||
| − | | | + | |<tt>├─📁 samples</tt> || Modules sample programs (VDP, PSG, Sprite, Print, etc.) |
|- | |- | ||
| − | | | + | |<tt>├─📁 targets</tt> || Samples to test all target (Plain ROM, Mapped ROM, DOS, etc.) |
|- | |- | ||
| − | | | + | |<tt>├─📁 template</tt> || MSX1 template program (can be use as base to create your new program) |
|- | |- | ||
| − | | | + | |<tt>└─📁 template_msx2</tt> || MSX2 template program (can be use as base to create your new program) |
|} | |} | ||
Revision as of 16:29, 25 December 2022
The MSXgl samples can be tested from their respective directories:
| 📁 projects | |
| ├─📁 samples | Modules sample programs (VDP, PSG, Sprite, Print, etc.) |
| ├─📁 targets | Samples to test all target (Plain ROM, Mapped ROM, DOS, etc.) |
| ├─📁 template | MSX1 template program (can be use as base to create your new program) |
| └─📁 template_msx2 | MSX2 template program (can be use as base to create your new program) |
Samples
Each sample have 2 files :
- .c with sample source code,
- .js with Build Tool option overwrite.
From the command-line you can execute build.bat (Windows) or ./build.sh (Linux) plus the name of one of the samples. "s_game" for example.
build s_game
You can also overwrite the target format (unless the sample needs a specific target):
build s_game DOS1
Note: If you have configured an emulator path in MSXgl\projects\default_config.cmd, you can edit project_config.js and change "DoRun = false;" to "DoRun = true;" to allow auto-launch of the built program.
Targets
TBC...
Template
TBC...