I've uploaded binaries for DOS and most of the standard library.
Note: a few things are still missing from the library, most notably: <time.h> functionality, *scanf() functions.
Everyone's welcome to play with the compiler and report bugs.
How to install the .zip file downloaded from
GitHub:
1. Create C:\SMLRC (any hard disk or name will do, but make the full path as short as possible) and copy into it the following subdirectories of the .zip file:
BIND
INCLUDE
LIB
TESTS
2. Include C:\SMLRC\BIND in the environment variable PATH
3. Don't forget to have NASM (2.10 is good) installed and also available via PATH
You should now be able to compile the following example from TESTS\hw.c:
Code:
/*
How to compile for DOS (all mode(l)s: tiny/.COM, small/.EXE, huge/.EXE):
smlrcc -dost hw.c -o hwdt.com
smlrcc -doss hw.c -o hwds.exe
smlrcc -dosh hw.c -o hwdh.exe
*/
#include <stdio.h>
int main(void)
{
puts("Hello, World!");
return 0;
}
I suggest to stick to the huge memory mode(l) as it supports 32-bit types such as long the functions that consume or return these types. In this mode(l) you can allocate all the available conventional memory via malloc() and you're not limited to objects smaller than 64KB.
The huge memory mode(l) is selected with the "-dosh" option, but you don't need to specify it explicitly when using a DOS version of smlrcc.
What else to know?
smlrcc can consume one or more of .c, .asm, .o or .a files and make an executable out of them.
If the command line is too long (over some 120 characters), you can put it into a file, say, mycmd.txt, and invoke smlrcc with @mycmd.txt (note the @ prefix) and it will extract the command line parameters from the file mycmd.txt. The linker (smlrl) supports this as well.
smlrcc supports the following useful options:
-c (compile only, don't link)
-S (compile to assembly only)
-v (verbose; show executed commands)
-map <mapfile> (produce the map file together with the binary)
You can compile your .c/.asm/.o files directly to a .a library file if you invoke smlrcc like so:
smlrcc [options] <file(s)> -c -o mylib.a
There's more but the documentation hasn't been updated for a while and so here I'm giving the most basic info only.
Enjoy.