Fixes for recent commits

The Makefile.example file now has the ALT_OBJ and ALT_TARGET (with a comment explaining how to use it) and the alt rule (which if the variables are left empty it will do nothing with 'make alt' or 'make everything'). The example Makefile now has the everything rule as well, for those who have an alt target. Fix links to next/try.sh, next/try.alt.sh and next/Makefile.example in html files (guidelines/rules/FAQ) to not link to GitHub as they're supposed to be downloaded.
2024-12-04 10:28:16 -08:00
1 parent c8109a6f8f
commit 154d40710b
@@ -893,7 +893,7 @@ this is not clear!</li>
 <p>If your submission has more than one use, or if you have interesting ways to
 invoke your program, perhaps using other commonly installed tools (or tools
 included in your submission), it can be helpful to include a <code>try.sh</code> script.</p>
-<p>A <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/try.sh">template try.sh</a> can be used as a
+<p>A <a href="next/try.sh">template try.sh</a> can be used as a
 starting point, or you can look at some of the others in the website, to get
 some ideas.</p>
 <p>It is not detrimental to your chances of winning if you do not include one as
@@ -903,7 +903,7 @@ does not mean that a program that cannot be used with other programs is less
 interesting or less likely to win, but we do enjoy interesting and creative uses
 of submissions.</p>
 <p>If you have alternate code that you are including, then you can use the
-<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/try.alt.sh">try.alt.sh template</a> instead.</p>
+<a href="next/try.alt.sh">try.alt.sh template</a> instead.</p>
 <p>We recommend that you include the use of these scripts in the <code>try</code> rule in the
 example Makefile that you modify for your submission. See the
 FAQ on “<a href="#makefile">submission Makefiles</a>.</p>
@@ -580,7 +580,7 @@ If your submission has more than one use, or if you have interesting ways to
 invoke your program, perhaps using other commonly installed tools (or tools
 included in your submission), it can be helpful to include a `try.sh` script.

-A [template try.sh](%%REPO_URL%%/next/try.sh) can be used as a
+A [template try.sh](next/try.sh) can be used as a
 starting point, or you can look at some of the others in the website, to get
 some ideas.

@@ -592,7 +592,7 @@ interesting or less likely to win, but we do enjoy interesting and creative uses
 of submissions.

 If you have alternate code that you are including, then you can use the
-[try.alt.sh template](%%REPO_URL%%/next/try.alt.sh) instead.
+[try.alt.sh template](next/try.alt.sh) instead.

 We recommend that you include the use of these scripts in the `try` rule in the
 example Makefile that you modify for your submission. See the
@@ -130,6 +130,16 @@ endif
 PROG= prog
 OBJ= ${PROG}.o
 TARGET= ${PROG}
+# If you have alternate code, try something like:
+# ALT_OBJ= ${PROG}.alt.o
+# ALT_TARGET= ${PROG}.alt
+#
+# or so.
+#
+# Please remove these lines either way.
+#
+ALT_OBJ=
+ALT_TARGET=

 # list any data files supplied with the submission
 #
@@ -150,11 +160,27 @@ all: data ${TARGET}
 ${PROG}: ${PROG}.c
 	${CC} ${CFLAGS} $< -o $@ ${LDFLAGS}

+# alternative executable
+#
+alt: data ${ALT_TARGET}
+	@${TRUE}
+
+${PROG}.alt: ${PROG}.alt.c
+	${CC} ${CFLAGS} $< -o $@ ${LDFLAGS}
+
+
+
 # data files
 #
 data: ${DATA}
 	@${TRUE}

+# both all and alt
+#
+everything: all alt
+	@${TRUE}
+
+
 # one suggested way to run the program
 #
 try: ${PROG} ${DATA}
@@ -465,7 +465,7 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
 </div>
 </div>
 <p class="leftbar">
-These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.24 2024-12-02</strong>.
+These <a href="guidelines.html">IOCCC guidelines</a> are version <strong>28.25 2024-12-04</strong>.
 </p>
 <p><strong>IMPORTANT</strong>: Be <strong>SURE</strong> to read the <a href="rules.html">IOCCC rules</a>.</p>
 <p>Jump to: <a href="#">top</a></p>
@@ -551,7 +551,7 @@ repo</a>.
 to account for the new <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a> tools.
 </p>
 <p class="leftbar">
-You <strong>are encouraged</strong> to use <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">this
+You <strong>are encouraged</strong> to use <a href="Makefile.example">this
 Makefile.example</a>,
 rather than the one at the <code>mkiocccentry</code> repo.
 </p>
@@ -939,14 +939,14 @@ that’s OK too!
 <h1 id="makefiles">Makefiles</h1>
 </div>
 <p class="leftbar">
-<p>We <strong>recommend</strong> that you use the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example
+<p>We <strong>recommend</strong> that you use the <a href="Makefile.example">example
 Makefile</a>,
 renamed as <code>Makefile</code> of course, as the starting point for your submission’s
 required <code>Makefile</code>. Feel free to modify the <code>Makefile</code> to suit your obfuscated
 needs.</p>
 <p class="leftbar">
 The rest of this section will assume that you are using some variant of the
-<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example Makefile</a>,
+<a href="Makefile.example">example Makefile</a>,
 renamed as <code>Makefile</code> of course.
 </p>
 <p class="leftbar">
@@ -1089,7 +1089,7 @@ Again, please note that in macOS, <code>/usr/bin/gcc</code> is actually <code>cl
 </div>
 <p class="leftbar">
 We <strong>LIKE</strong> submissions that use an edited variant of the
-<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example Makefile</a>,
+<a href="Makefile.example">example Makefile</a>,
 renamed as <code>Makefile</code> of course. This makes it easier for the <a href="../judges.html">IOCCC Judges</a>
 to test your submission. And if your submissions wins, it makes it easier to integrate it into
 the <a href="https://www.ioccc.org/index.html">Official IOCCC winner website</a>.
@@ -1102,11 +1102,12 @@ example script). Of course, it is quite possible that only one invocation is
 possible, so it is not necessarily detrimental to your submission if you do not
 include one, though we do like interesting and creative uses of submissions. See
 also the
+FAQ on “<a href="../faq.html#try_scripts">submitting try.sh and try.alt.sh scripts</a>”.
 </p>
 <p class="leftbar">
-You might wish to add <code>./try.sh</code>, and if you have alternate code,
-<code>./try.alt.sh</code>, to the <code>try</code> rule in the Makefile you submit. See also the
-FAQ on “<a href="../faq.html#try_scripts">submitting try.sh and try.alt.sh scripts</a>”.
+You might wish to add <code>./try.sh</code> to the <code>try</code> rule in the Makefile you submit.
+If you have alternate code, then you could add a <code>try.alt</code> rule or something
+like that.
 </p>
 <p>Doing masses of <code>#define</code>s to obscure the source has become ‘old’. We
 tend to ‘see thru’ masses of <code>#define</code>s due to our pre-processor tests
@@ -1340,7 +1341,7 @@ they do not work as documented.</p>
 is NOT the smallest C source file that when compiled and run, dumps core:</p>
 <pre><code>    main;</code></pre>
 <p class="leftbar">
-Unless you specify <code>-fwritable-strings</code> (see <code>COTHER</code> in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example
+Unless you specify <code>-fwritable-strings</code> (see <code>COTHER</code> in the <a href="Makefile.example">example
 Makefile</a>)
 do not assume this sort of code will work:
 </p>
@@ -1563,8 +1564,9 @@ CPU, we might just try your submission on that emulator as well :-)
 <p class="leftbar">
 If your submission <strong>MUST</strong> run only on a 64-bit or 32-bit architecture,
 then you <strong>MUST</strong> specify the <code>-arch</code> on your command line
-(see <code>ARCH</code> in the <a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">example
-Makefile</a>). Do not assume a processor word size without specifying <code>-arch</code>. For example:
+(see <code>ARCH</code> in the <a href="Makefile.example">example
+Makefile</a>). Do not assume a processor word size without
+specifying <code>-arch</code>. For example:
 </p>
 <pre><code>    ARCH= -m64</code></pre>
 <p class="leftbar">
@@ -52,7 +52,7 @@ Jump to: [top](#)
 </div>

 <p class="leftbar">
-These [IOCCC guidelines](guidelines.html) are version **28.24 2024-12-02**.
+These [IOCCC guidelines](guidelines.html) are version **28.25 2024-12-04**.
 </p>

 **IMPORTANT**: Be **SURE** to read the [IOCCC rules](rules.html).
@@ -161,7 +161,7 @@ to account for the new [mkiocccentry repo](https://github.com/ioccc-src/mkioccce

 <p class="leftbar">
 You **are encouraged** to use [this
-Makefile.example](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example),
+Makefile.example](Makefile.example),
 rather than the one at the `mkiocccentry` repo.
 </p>

@@ -647,14 +647,14 @@ that's OK too!

 <p class="leftbar">
 We **recommend** that you use the [example
-Makefile](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example),
+Makefile](Makefile.example),
 renamed as `Makefile` of course, as the starting point for your submission's
 required `Makefile`.  Feel free to modify the `Makefile` to suit your obfuscated
 needs.

 <p class="leftbar">
 The rest of this section will assume that you are using some variant of the
-[example Makefile](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example),
+[example Makefile](Makefile.example),
 renamed as `Makefile` of course.
 </p>

@@ -860,7 +860,7 @@ Jump to: [top](#)

 <p class="leftbar">
 We **LIKE** submissions that use an edited variant of the
-[example Makefile](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example),
+[example Makefile](Makefile.example),
 renamed as `Makefile` of course.  This makes it easier for the [IOCCC Judges](../judges.html)
 to test your submission. And if your submissions wins, it makes it easier to integrate it into
 the [Official IOCCC winner website](https://www.ioccc.org/index.html).
@@ -874,12 +874,13 @@ example script). Of course, it is quite possible that only one invocation is
 possible, so it is not necessarily detrimental to your submission if you do not
 include one, though we do like interesting and creative uses of submissions. See
 also the
+FAQ on "[submitting try.sh and try.alt.sh scripts](../faq.html#try_scripts)".
 </p>

 <p class="leftbar">
-You might wish to add `./try.sh`, and if you have alternate code,
-`./try.alt.sh`, to the `try` rule in the Makefile you submit. See also the
-FAQ on "[submitting try.sh and try.alt.sh scripts](../faq.html#try_scripts)".
+You might wish to add `./try.sh` to the `try` rule in the Makefile you submit.
+If you have alternate code, then you could add a `try.alt` rule or something
+like that.
 </p>

 Doing masses of `#define`s to obscure the source has become 'old'.  We
@@ -1161,7 +1162,7 @@ is NOT the smallest C source file that when compiled and run, dumps core:

 <p class="leftbar">
 Unless you specify `-fwritable-strings` (see `COTHER` in the [example
-Makefile](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example))
+Makefile](Makefile.example))
 do not assume this sort of code will work:
 </p>

@@ -1426,7 +1427,8 @@ CPU, we might just try your submission on that emulator as well :-)
 If your submission **MUST** run only on a 64-bit or 32-bit architecture,
 then you **MUST** specify the `-arch` on your command line
 (see `ARCH` in the [example
-Makefile](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example)).  Do not assume a processor word size without specifying `-arch`.  For example:
+Makefile](Makefile.example)).  Do not assume a processor word size without
+specifying `-arch`.  For example:
 </p>

 ``` <!---make-->
@@ -466,7 +466,7 @@ writing by <a href="../contact.html">contacting the judges</a>.</p>
 </div>
 <p>Jump to: <a href="#">top</a></p>
 <p class="leftbar">
-These <a href="rules.html">IOCCC rules</a> are version <strong>28.11 2024-12-01</strong>.
+These <a href="rules.html">IOCCC rules</a> are version <strong>28.12 2024-12-04</strong>.
 </p>
 <p><strong>IMPORTANT</strong>: Be sure to read the <a href="guidelines.html">IOCCC guidelines</a>.</p>
 <p>Jump to: <a href="#">top</a></p>
@@ -905,7 +905,7 @@ those requirements.
 <p class="leftbar">
 The <code>Makefile</code> <strong>MUST</strong> be a <strong>non</strong>-empty file in <strong><a href="https://www.gnu.org/software/make/manual/make.html">GNU
 Makefile</a></strong> form. See the
-<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">Makefile.example</a>,
+<a href="Makefile.example">Makefile.example</a>,
 the
 FAQ on “<a href="../faq.html#submission_makefiles">submission Makefile</a>”
 and the
@@ -1092,7 +1092,7 @@ make(1) compatibility the IOCCC
 supports</a> for more details.</p>
 <p class="leftbar">
 You are <strong>ENCOURAGED</strong> to use
-<a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example">Makefile.example</a>,
+<a href="Makefile.example">Makefile.example</a>,
 renamed as <code>Makefile</code> of course, for help in constructing your <code>Makefile</code>.
 </p>
 <p>The target of the Makefile must be called <code>prog</code>. The original
@@ -57,7 +57,7 @@ Jump to: [top](#)
 Jump to: [top](#)

 <p class="leftbar">
-These [IOCCC rules](rules.html) are version **28.11 2024-12-01**.
+These [IOCCC rules](rules.html) are version **28.12 2024-12-04**.
 </p>

 **IMPORTANT**: Be sure to read the [IOCCC guidelines](guidelines.html).
@@ -595,7 +595,7 @@ It is generated by the `mkiocccentry(1)` tool.
 You submission may have additional files, however the filenames of those additional files **MUST**:
 </p>

-* <p class="leftbar"> Be less than **100** characters in length.</p>
+* <p class="leftbar">Be less than **100** characters in length.</p>
 * <p class="leftbar">Match the regular expression:
 `^[0-9A-Za-z][0-9A-Za-z._+-]*$`</p>

@@ -607,7 +607,7 @@ those requirements.
 <p class="leftbar">
 The `Makefile` **MUST** be a **non**-empty file in **[GNU
 Makefile](https://www.gnu.org/software/make/manual/make.html)** form. See the
-[Makefile.example](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example),
+[Makefile.example](Makefile.example),
 the
 FAQ on "[submission Makefile](../faq.html#submission_makefiles)"
 and the
@@ -812,7 +812,7 @@ supports](../faq.html#make_compatibility) for more details.

 <p class="leftbar">
 You are **ENCOURAGED** to use
-[Makefile.example](https://github.com/ioccc-src/temp-test-ioccc/blob/master/next/Makefile.example),
+[Makefile.example](Makefile.example),
 renamed as `Makefile` of course, for help in constructing your `Makefile`.
 </p>