CCFLAGS += /nologo /W4 /GX /YX ;
C++FLAGS = $(CCFLAGS) ;
LINKFLAGS += /NODEFAULTLIB ;
LINKLIBS = $(MSVCNT)\\lib\\advapi32.lib
$(MSVCNT)\\lib\\libc.lib
$(MSVCNT)\\lib\\oldnames.lib
$(MSVCNT)\\lib\\user32.lib
$(MSVCNT)\\lib\\kernel32.lib ;
if $(Debug) = yes
{
CCFLAGS += /Zi /MLd ;
LINKFLAGS += -debug:full /PROFILE ;
}
else
{
CFLAGS += /Ox ;
}
Main jamshell : jamshell.c ;
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #1 | 1182 | Matt Armstrong |
This is a shell suitable for use as a JAMSHELL on Windows NT. If you increace MAXLINES in jam.h to 10000 for Windows NT, you'll find that CMD.EXE no longer serves as a useful default shell because its built in commands such as del and echo can't handle such long command lines. This shell does two things: Implements jamshell-echo and jamshell-erase commands that do the job of CMD.EXE's echo and del commands. This way, very long lists of files can be deleted in one go. Checks if the command is a single line that contains no shell meta characters, and if so it runs the command directly. By bypassing CMD.EXE, very long command lines can be executed. Otherwise, it shells out to CMD.EXE to run the command. |