Samples cleanup

This commit is contained in:
Wayne Parham
2021-06-07 00:48:02 -05:00
parent a3fce656b7
commit 975e43892f
10 changed files with 0 additions and 947 deletions

View File

@@ -1,36 +0,0 @@
#!/usr/bin/env bash
#
# build.sh
if [ -f $1.c ]; then
echo
echo "--- Building $1 ---"
if [ -f $1.s ]; then
rm $1.s
fi
if [ -f $1.o ]; then
rm $1.o
fi
if [ -f $1.bin ]; then
rm $1.bin
fi
if [ -f $1.hex ]; then
rm $1.hex
fi
cc65 -t sym1 -O $1.c
ca65 $1.s
ld65 -C sym1.cfg -m $1.map -o $1.bin $1.o sym1.lib
if [ -f $1.bin ]; then
bin2hex $1.bin $1.hex > /dev/null 2>&1
fi
if [ -f $1.hex ]; then
echo "--- $1.hex made ---"
else
echo "--- $1.hex FAIL ---"
fi
fi

View File

@@ -1,36 +0,0 @@
#!/usr/bin/env bash
#
# build.sh
if [ -f $1.c ]; then
echo
echo "--- Building $1 ---"
if [ -f $1.s ]; then
rm $1.s
fi
if [ -f $1.o ]; then
rm $1.o
fi
if [ -f $1.bin ]; then
rm $1.bin
fi
if [ -f $1.hex ]; then
rm $1.hex
fi
cc65 -t sym1 -O $1.c
ca65 $1.s
ld65 -C sym1-32k.cfg -m $1.map -o $1.bin $1.o sym1.lib
if [ -f $1.bin ]; then
bin2hex $1.bin $1.hex > /dev/null 2>&1
fi
if [ -f $1.hex ]; then
echo "--- $1.hex made ---"
else
echo "--- $1.hex FAIL ---"
fi
fi

View File

@@ -1,36 +0,0 @@
#!/usr/bin/env bash
#
# build.sh
if [ -f $1.c ]; then
echo
echo "--- Building $1 ---"
if [ -f $1.s ]; then
rm $1.s
fi
if [ -f $1.o ]; then
rm $1.o
fi
if [ -f $1.bin ]; then
rm $1.bin
fi
if [ -f $1.hex ]; then
rm $1.hex
fi
cc65 -t sym1 -O $1.c
ca65 $1.s
ld65 -C sym1-4k.cfg -m $1.map -o $1.bin $1.o sym1.lib
if [ -f $1.bin ]; then
bin2hex $1.bin $1.hex > /dev/null 2>&1
fi
if [ -f $1.hex ]; then
echo "--- $1.hex made ---"
else
echo "--- $1.hex FAIL ---"
fi
fi

View File

@@ -1,14 +0,0 @@
#!/usr/bin/env bash
#
# clean.sh
if [ -f $1.c ]; then
echo
echo "--- Cleaning $1 ---"
rm $1.s $1.o $1.map $1.bin $1.hex > /dev/null 2>&1
echo "--- Cleaned $1 ---"
fi

View File

@@ -1,11 +0,0 @@
These simple build scripts can be used to build any single-file C program
you might write. Notice the diference in the linker line for the 4k build
compared with the 32k build. Small programs can be compiled with either
build script, but they won't run on a 4k machine if compiled for a 32k
system. So if you have a program that's small enough to fit in 4k, it is
probably better to build with the 4k script so it will run on Sym-1 machines
that do not have an expansion memory board.
Usage: build <program> (don't include the .c extension)
clean <program> (removes intermediate and output files)