Move Makefile.entry to Makefile.example
The file template/entry/Makefile.entry was moved to next/Makefile.example. This matches the mkiocccentry repo in filename and where it was before (template/entry) is not the right place as that is for the template of making submissions into a winning entry whereas next/ is for the next contest. The next/ seems like the most logical place because the example file could be updated per contest for whatever reason, perhaps by adding the year in it (or not). On the other hand, the try.sh in template/entry is for submitters too but since the bin/cvt-submission.sh script will copy the template files to a winning entry if it does not exist it is left in template/entry, even if this might not be ideal. The references to the old Makefile.entry have been updated to Makefile.example in the new path/filename. Other changes had to be made too including updates to bin/cvt-submission.sh. That script should be checked to make sure everything is okay but as I have no way to test it that might have to be done by the judges though I think it is okay. Html files that have been changed that might need to be checked are: 0. faq.html (this one especially should be checked) 1. next/guidelines.html (though the judges will be checking this more) 2. next/rules.html (though the judges will be checking this more) For the faq.html file, the Makefile.example and try.sh/try.alt.sh scripts should be downloaded, not linked to on GitHub and it needs to be clear that one should use the Makefile.example from the website (this repo) rather than the out of date mkiocccentry repo. For the guidelines and rules, and especially the guidelines, any files linked should also be downloaded and not linked to GitHub. The text should be clear already but it might be good to have a quick pass. The judges will be going over these files before the next contest too. The files should be downloaded here too, not linked to GitHub as submitters need to download the files to make use of. The thanks-for-help.html file was slightly modified but should be fine too. In this case the GitHub file should be linked to. The version of the rules and guidelines are from an earlier date of when they were last modified for the above changes (as this was worked on over a number of days).
This commit is contained in:
Cody Boone Ferguson committed
1 parent
ac765e1f4e
commit
a7f9b06350
12 files changed
+228
-88
No files matched your search
@@ -1,215 +0,0 @@
|
||||
#!/usr/bin/env make
|
||||
#
|
||||
# prog - an example Makefile <<=== change "an example Makefile" to a suitable title for entry
|
||||
#
|
||||
# Please copy this file into your entry directory under the name: Makefile
|
||||
# Modify the resulting Makefile as needed.
|
||||
|
||||
|
||||
#############################
|
||||
# shell used by this Makefile
|
||||
#############################
|
||||
#
|
||||
SHELL= bash
|
||||
|
||||
|
||||
#######################
|
||||
# common tool locations
|
||||
#######################
|
||||
#
|
||||
CC= cc
|
||||
GINDENT= gindent
|
||||
MV= mv
|
||||
RM= rm
|
||||
TRUE= true
|
||||
|
||||
# Common C compiler warnings to silence
|
||||
#
|
||||
# Example: CSILENCE= -Wno-some-thing -Wno-another-thing
|
||||
#
|
||||
# NOTE: If you add -Wno-stuff to CSILENCE, please update
|
||||
# CUNKNOWN in the next comment block.
|
||||
#
|
||||
# NOTE: Please don't add -Wno-unknown-warning-option to CSILENCE.
|
||||
#
|
||||
#
|
||||
CSILENCE=
|
||||
|
||||
# Attempt to silence unknown warnings
|
||||
#
|
||||
# If you add -Wno-stuff to CSILENCE, then please change CUNKNOWN to read:
|
||||
#
|
||||
# CUNKNOWN= -Wno-unknown-warning-option
|
||||
#
|
||||
CUNKNOWN=
|
||||
|
||||
# Common C compiler warning flags
|
||||
#
|
||||
CWARN= -Wall -Wextra -pedantic ${CSILENCE} ${CUNKNOWN}
|
||||
|
||||
# The standard to compile against
|
||||
#
|
||||
# Your IOCCC submission is free to require older C standards, or
|
||||
# even not specify a C standard at all. We suggest trying
|
||||
# for -std=gnu17, but that is not a requirement and you won't
|
||||
# be penalized if you name CSTD empty or use another
|
||||
# well known and reasonably widely implemented C standard.
|
||||
#
|
||||
CSTD= -std=gnu17
|
||||
|
||||
# Compiler bit architecture
|
||||
#
|
||||
# Example for 32-bitness: ARCH= -m32
|
||||
# Example for 64-bitness: ARCH= -m64
|
||||
#
|
||||
# NOTE: Normally one should not specify a specific architecture.
|
||||
#
|
||||
ARCH=
|
||||
|
||||
# Defines that are needed to compile
|
||||
#
|
||||
# Example: -Dfoo -Dbar=baz
|
||||
#
|
||||
CDEFINE=
|
||||
|
||||
# Include files that are needed to compile
|
||||
#
|
||||
# Example: CINCLUDE= -include stdio.h
|
||||
#
|
||||
CINCLUDE=
|
||||
|
||||
# Other flags to pass to the C compiler
|
||||
#
|
||||
# Example: COTHER= -fno-math-errno
|
||||
#
|
||||
COTHER=
|
||||
|
||||
# Optimization
|
||||
#
|
||||
OPT= -O3 -g3
|
||||
|
||||
# Default flags for ANSI C compilation
|
||||
#
|
||||
CFLAGS= ${CSTD} ${CWARN} ${ARCH} ${CDEFINE} ${CINCLUDE} ${COTHER} ${OPT}
|
||||
|
||||
# Libraries needed to build
|
||||
#
|
||||
LDFLAGS=
|
||||
|
||||
# C compiler to use
|
||||
#
|
||||
CC= cc
|
||||
|
||||
# Compiler add-ons or replacements for clang only
|
||||
#
|
||||
ifeq "$(findstring $(CLANG),${CC})" "$(CLANG)"
|
||||
#
|
||||
CSILENCE+=
|
||||
#
|
||||
CWARN+= -Weverything
|
||||
#
|
||||
endif
|
||||
|
||||
# Specific add-ons or replacements for gcc only
|
||||
#
|
||||
ifeq "$(findstring $(GCC),${CC})" "$(GCC)"
|
||||
#
|
||||
CSILENCE+=
|
||||
#
|
||||
CWARN+=
|
||||
#
|
||||
endif
|
||||
|
||||
|
||||
###########################################
|
||||
# Special Makefile variables for this entry
|
||||
###########################################
|
||||
|
||||
# what to build
|
||||
#
|
||||
PROG= prog
|
||||
OBJ= ${PROG}.o
|
||||
TARGET= ${PROG}
|
||||
|
||||
# list any data files supplied with the submission
|
||||
#
|
||||
DATA=
|
||||
|
||||
|
||||
#################
|
||||
# build the entry
|
||||
#################
|
||||
#
|
||||
all: data ${TARGET}
|
||||
@${TRUE}
|
||||
|
||||
.PHONY: all data try clean clobber install
|
||||
|
||||
# how to compile
|
||||
#
|
||||
${PROG}: ${PROG}.c
|
||||
${CC} ${CFLAGS} $< -o $@ ${LDFLAGS}
|
||||
|
||||
# data files
|
||||
#
|
||||
data: ${DATA}
|
||||
@${TRUE}
|
||||
|
||||
# one suggested way to run the program
|
||||
#
|
||||
try: ${PROG} ${DATA}
|
||||
@# remove these comments
|
||||
@# notice how we do not assume that . is a component of the $PATH environment variable
|
||||
@# change this next line as needed
|
||||
./${PROG} some arguments
|
||||
|
||||
|
||||
###############
|
||||
# utility rules
|
||||
###############
|
||||
#
|
||||
clean:
|
||||
${RM} -f ${OBJ}
|
||||
@-if [[ -f indent.c ]]; then \
|
||||
echo ${RM} -f indent.c; \
|
||||
${RM} -f indent.c; \
|
||||
fi
|
||||
|
||||
clobber: clean
|
||||
${RM} -f ${TARGET}
|
||||
@-if [[ -e sandwich ]]; then \
|
||||
${RM} -f sandwich; \
|
||||
echo 'ate sandwich'; \
|
||||
fi
|
||||
|
||||
# Do not install prog, please!
|
||||
#
|
||||
install:
|
||||
@echo "Dr. Spock says that is not logical!"
|
||||
@${TRUE}
|
||||
|
||||
# you may be able to misunderstand the source by reading indent.c
|
||||
#
|
||||
indent.c: ${PROG}.c
|
||||
@if which "${GINDENT}" >/dev/null 2>&1; then \
|
||||
echo ${RM} -f $@; \
|
||||
${RM} -f $@; \
|
||||
echo "${GINDENT} < $< > $@"; \
|
||||
${GINDENT} < $< > $@; \
|
||||
elif which "${INDENT}" >/dev/null 2>&1; then \
|
||||
echo ${RM} -f $@; \
|
||||
${RM} -f $@; \
|
||||
echo "${INDENT} < $< > $@"; \
|
||||
${INDENT} < $< > $@; \
|
||||
else \
|
||||
echo "no indent tool found, ident $< yourself, sorry"; \
|
||||
echo "exit 17"; \
|
||||
exit 17; \
|
||||
fi
|
||||
|
||||
|
||||
######################################
|
||||
# optional include of 1337 hacker rulz
|
||||
######################################
|
||||
|
||||
-include 1337.mk ../1337.mk ../../1337.mk
|
||||
+39
-15
@@ -1,32 +1,56 @@
|
||||
#!/usr/bin/env bash
|
||||
#
|
||||
# try.sh - demonstrate IOCCC entry abstract alternate code
|
||||
#
|
||||
# NOTE: if your submission wins and become an entry, 'abstract' will be changed
|
||||
# to the YYYY/directory name. You can remove this comment if you wish but if not
|
||||
# it'll be done by the judges.
|
||||
# try.alt.sh - demonstrate IOCCC entry YYYY/foo alternate code
|
||||
# XXX - try.alt.sh example version: 1.0.0-1 11-28-2024 - XXX
|
||||
#
|
||||
# XXX - NOTE: if your submission wins and become an entry, then - XXX
|
||||
# XXX - YYYY/foo will be changed to the 4 digit year and directory - XXX
|
||||
# XXX - name. - XXX
|
||||
# XXX - NOTE: please remove the XXX lines in this file, including this one - XXX
|
||||
|
||||
# make sure CC is set so that when we do make CC="$CC" it isn't empty. Doing it
|
||||
# this way allows us to have the user specify a different compiler in an easy
|
||||
# way.
|
||||
if [[ -z "$CC" ]]; then
|
||||
CC="cc"
|
||||
fi
|
||||
# XXX - if you need CC to be something else for some reason, say clang, - XXX
|
||||
# XXX - then change "cc" to that or whatever you need. - XXX
|
||||
# XXX - If you need other variables you can also set them in whatever way - XXX
|
||||
# XXX - you need; this is a good method, however, in cases where it's OK - XXX
|
||||
# XXX - to let the user redefine it. - XXX
|
||||
[[ -z "$CC" ]] && CC="cc"
|
||||
|
||||
# XXX - make sure to compile the alt code, using make alt! - XXX
|
||||
# XXX - if you need to build the main program for the try.alt.sh script, - XXX
|
||||
# XXX - then change the 'alt' to 'all alt' in the below command. - XXX
|
||||
# XXX - Later, if the submission wins, it can be changed to 'everything'. - XXX
|
||||
make CC="$CC" alt >/dev/null || exit 1
|
||||
|
||||
# XXX - it's usually a good idea to clear the screen but if not done - XXX
|
||||
# XXX - then you should remove the comment about it and the command. - XXX
|
||||
# clear screen after compilation so that only the entry is shown
|
||||
clear
|
||||
|
||||
# XXX - Invoke the program in one or more ways - XXX
|
||||
# XXX - It is good to use the shell built-in read to let the user - XXX
|
||||
# XXX - read what will happen and then proceed as they wish. - XXX
|
||||
# XXX - You may modify the command based on your program and you - XXX
|
||||
# XXX - may provide more than one invocation. - XXX
|
||||
# XXX - Please remove the XXX lines - XXX
|
||||
# XXX - an example follows - XXX
|
||||
# XXX - Invoke the program in one or more ways - XXX
|
||||
|
||||
# XXX - NOTE: you can include more than one command line and you - XXX
|
||||
# XXX - certainly can include pipelines. - XXX
|
||||
|
||||
# XXX - It is good to use the shell built-in read(1) to - XXX
|
||||
# XXX - let the user know what is about to be done, as - XXX
|
||||
# XXX - shown below, so they can proceed when ready. - XXX
|
||||
|
||||
# XXX - You may modify the command based on your program and you - XXX
|
||||
# XXX - may provide more than one invocation. - XXX
|
||||
|
||||
# XXX - Examples follow. - XXX
|
||||
|
||||
# XXX - if the prompt will not be too long, say more than 80 chars - XXX
|
||||
# XXX - or so: - XXX
|
||||
read -r -n 1 -p "Press any key to run: ./prog.alt: "
|
||||
echo 1>&2
|
||||
./prog.alt
|
||||
|
||||
# XXX - Otherwise, for longer command lines, you might try: - XXX
|
||||
echo "$ ./prog.alt some long command line"
|
||||
read -r -n 1 -p "Press any key to continue: "
|
||||
./prog.alt some long command line
|
||||
|
||||
+40
-15
@@ -1,32 +1,57 @@
|
||||
#!/usr/bin/env bash
|
||||
#
|
||||
# try.sh - demonstrate IOCCC entry abstract
|
||||
#
|
||||
# NOTE: if your submission wins and become an entry, 'abstract' will be changed
|
||||
# to the YYYY/directory name. You can remove this comment if you wish but if not
|
||||
# it'll be done by the judges.
|
||||
# try.sh - demonstrate IOCCC entry YYYY/foo
|
||||
# XXX - try.sh example version: 1.0.0-1 11-28-2024 - XXX
|
||||
|
||||
# XXX - NOTE: if your submission wins and become an entry, then - XXX
|
||||
# XXX - YYYY/foo will be changed to the 4 digit year and directory - XXX
|
||||
# XXX - name. - XXX
|
||||
# XXX - NOTE: please remove the XXX lines in this file, including this one - XXX
|
||||
#
|
||||
|
||||
# make sure CC is set so that when we do make CC="$CC" it isn't empty. Doing it
|
||||
# this way allows us to have the user specify a different compiler in an easy
|
||||
# way.
|
||||
if [[ -z "$CC" ]]; then
|
||||
CC="cc"
|
||||
fi
|
||||
# XXX - if you need CC to be something else, say clang, then change cc - XXX
|
||||
# XXX - to whatever you need. - XXX
|
||||
# XXX - If you need other variables you can also set them in whatever way - XXX
|
||||
# XXX - you need; this is a good method, however, in cases where it's OK - XXX
|
||||
# XXX - to let the user redefine it. - XXX
|
||||
[[ -z "$CC" ]] && CC="cc"
|
||||
|
||||
|
||||
# XXX - make sure to compile the program, using make all! - XXX
|
||||
# XXX - if you need to build the alt code for the try.sh script, - XXX
|
||||
# XXX - then change the 'all' to 'all alt' in the below command. - XXX
|
||||
# XXX - Later, if the submission wins, it can be changed to 'everything'. - XXX
|
||||
make CC="$CC" all >/dev/null || exit 1
|
||||
|
||||
# XXX - it's usually a good idea to clear the screen but if not done - XXX
|
||||
# XXX - then you should remove the comment about it and the command. - XXX
|
||||
# clear screen after compilation so that only the entry is shown
|
||||
clear
|
||||
|
||||
# XXX - Invoke the program in one or more ways - XXX
|
||||
# XXX - It is good to use the shell built-in read to let the user - XXX
|
||||
# XXX - read what will happen and then proceed as they wish. - XXX
|
||||
# XXX - You may modify the command based on your program and you - XXX
|
||||
# XXX - may provide more than one invocation. - XXX
|
||||
# XXX - Please remove the XXX lines - XXX
|
||||
# XXX - an example follows - XXX
|
||||
# XXX - Invoke the program in one or more ways - XXX
|
||||
|
||||
# XXX - NOTE: you can include more than one command line and you - XXX
|
||||
# XXX - certainly can include pipelines. - XXX
|
||||
|
||||
# XXX - It is good to use the shell built-in read(1) to - XXX
|
||||
# XXX - let the user know what is about to be done, as - XXX
|
||||
# XXX - shown below, so they can proceed when ready. - XXX
|
||||
|
||||
# XXX - You may modify the command based on your program and you - XXX
|
||||
# XXX - may provide more than one invocation. - XXX
|
||||
|
||||
# XXX - Examples follow. - XXX
|
||||
|
||||
# XXX - if the prompt will not be too long, say more than 80 chars - XXX
|
||||
# XXX - or so: - XXX
|
||||
read -r -n 1 -p "Press any key to run: ./prog: "
|
||||
echo 1>&2
|
||||
./prog
|
||||
|
||||
# XXX - Otherwise, for longer command lines, you might try: - XXX
|
||||
echo "$ ./prog some long command line"
|
||||
read -r -n 1 -p "Press any key to continue: "
|
||||
./prog some long command line
|
||||
Reference in new issue
Block a user