Difference between revisions of "Testing library samples"

From MSX Game Library

(Samples)
(Samples)
Line 17: Line 17:
  
 
Each [[samples|sample]] have 2 files :
 
Each [[samples|sample]] have 2 files :
* <tt>.c</tt> with sample source code
+
* <tt>.c</tt> with sample source code,
* <tt>.cmd</tt> with Build Tool option overwrite
+
* <tt>.js</tt> with [[Build Tool]] option overwrite.
  
 
From the command-line you can execute <tt>build.bat</tt> (Windows) or <tt>./build.sh</tt> (Linux) plus the name of one of the [[samples]]. "s_game" for example.
 
From the command-line you can execute <tt>build.bat</tt> (Windows) or <tt>./build.sh</tt> (Linux) plus the name of one of the [[samples]]. "s_game" for example.

Revision as of 16:05, 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...