blog:ql_dev1

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
blog:ql_dev1 [2021/12/15 19:50] – [Working with QL files & devices] johnblog:ql_dev1 [2021/12/16 11:03] (current) john
Line 23: Line 23:
    * {{ :blog:sinclair:c68_linux64-2021_12_14.tgz |}} - Pre-compiled, with headers and runtime libraries. Unpacks to ///opt/toolchains/qdos//    * {{ :blog:sinclair:c68_linux64-2021_12_14.tgz |}} - Pre-compiled, with headers and runtime libraries. Unpacks to ///opt/toolchains/qdos//
    * {{ :blog:sinclair:c68.pdf |}} - C68 User Manual. For the original Sinclair QL hosted version, but most of the compiler and linker flags and options remain the same.    * {{ :blog:sinclair:c68.pdf |}} - C68 User Manual. For the original Sinclair QL hosted version, but most of the compiler and linker flags and options remain the same.
 +   * {{ :blog:sinclair:c68_documentation_-_dave_walker.pdf |}} - A more in-depth manual about the use of C68, including a //basic// reference of available calls.
  
 === Sample C68 Makefile === === Sample C68 Makefile ===
Line 236: Line 237:
 </code> </code>
  
-... the value printed is the size of the dataspace needed.+... the value printed is the size of the dataspace needed. So you would then copy and mark your binary with qltools as follows: 
 + 
 +<code> 
 +$ xtcc game.bin 
 +868 
 +$ qltools floppy.img -W game.bin 
 +$ qltools floppy.img -x game.bin 868 
 +</code> 
 + 
 +Or even easier, embed the xtcc call in backticks: 
 + 
 +<code> 
 +$ qltools floppy.img -W game.bin 
 +$ qltools floppy.img -x game.bin `xtcc game.bin` 
 +</code> 
  • blog/ql_dev1.1639597848.txt.gz
  • Last modified: 2021/12/15 19:50
  • by john