66 * v. 2.0. If a copy of the MPL was not distributed with this file, You can
77 * obtain one at https://mozilla.org/MPL/2.0/
88 *
9- * Copyright (C) 2009-2023 , Peter Johnson (gravatar.com/delphidabbler).
9+ * Copyright (C) 2009-2024 , Peter Johnson (gravatar.com/delphidabbler).
1010 *
1111 * Instructions for building CodeSnip from source.
1212-->
@@ -513,12 +513,14 @@ <h3>
513513 | +-- exe - receives executable code and compiled help file
514514 | |
515515 | +-- release - receives release files
516+ | |
517+ | +-- ~tmp~ - store for temp files ceated in release process
516518 |
517519 ...</ pre >
518520
519521< p >
520522 If the < code > _build/bin</ code > folder already existed, it will have been emptied.
521- In addition, < code > Make</ code > will have created a < code > .cfg</ code > file from
523+ In addition, < code > Make</ code > will have created a < code > .cfg</ code > file from a
522524 template in the < code > Src</ code > folder. This < code > .cfg</ code > file is needed
523525 for DCC32 to run correctly. The file will be ignored by Git.
524526</ p >
580582 You have several options:
581583</ p >
582584
583- < ul class ="spaced ">
585+ < ol class ="spaced ">
584586 < li >
585587 Build the < em > CodeSnip</ em > Executable
586588 </ li >
@@ -599,10 +601,10 @@ <h2>
599601 < li >
600602 Clean Up.
601603 </ li >
602- </ ul >
604+ </ ol >
603605
604606< p >
605- Each of these options is described below. All except the last assume that
607+ Each of these options is described below. All except options 5 and 6 assume that
606608 < code > Make config</ code > has been run.
607609</ p >
608610
648650< pre class ="cmd "> < span class ="prompt "> ></ span > Make -DPORTABLE codesnip</ pre >
649651
650652< p >
651- Again the executable is placed in the < code > _build/ exe</ code > folder, but this time
653+ Again the executable is placed in the < code > _build\ exe</ code > folder, but this time
652654 it is named < code > CodeSnip-p.exe</ code >
653655</ p >
654656
@@ -665,12 +667,17 @@ <h3>
665667< p >
666668 The compiled help file will be written to the < code > _build\exe</ code > folder.
667669</ p >
670+
671+ < p >
672+ The same help file is used for the standard and portable editions.
673+ </ p >
674+
668675< h3 >
669676 Build the Setup Program
670677</ h3 >
671678
672679< p >
673- The setup program requires that the < em > CodeSnip</ em > excutable and the
680+ The setup program requires that the < em > CodeSnip</ em > executable and the
674681 compiled help file are already present in the < code > _build\exe</ code > directory.
675682</ p >
676683
690697< p >
691698 The setup program is named < code > CodeSnip-Setup-x.x.x.exe</ code > , where
692699 x.x.x is the version number extracted from < em > CodeSnip</ em > 's version
693- information. It is placed in the < code > _build/ exe</ code > directory.
700+ information. It is placed in the < code > _build\ exe</ code > directory.
694701</ p >
695702
696703< p >
715722
716723< p >
717724 Make can create zip files containing all the files that are included in a release.
718- Zip files are written to the < code > _build/ release</ code > directory.
725+ Zip files are written to the < code > _build\ release</ code > directory.
719726</ p >
720727
721728< h4 >
@@ -724,12 +731,12 @@ <h4>
724731
725732< p >
726733 The release zip file for the standard edition requires that the setup files is already
727- present in the < code > _build/ exe</ code > directory.
734+ present in the < code > _build\ exe</ code > directory.
728735</ p >
729736
730737< p >
731738 The release file includes the setup file along with < code > ReadMe.txt</ code >
732- that is automatically generated from < code > Docs/ ReadMe-standard.txt</ code > .
739+ that is automatically generated from < code > Docs\ ReadMe-standard.txt</ code > .
733740</ p >
734741
735742< p >
763770
764771< p >
765772 The release file includes the portable executable file, < code > CodeSnip-p.exe</ code > ,
766- the help file < code > CodeSnip.chm</ code > , < code > Docs/ License.html</ code > and
773+ the help file < code > CodeSnip.chm</ code > , < code > Docs\ License.html</ code > and
767774 < code > ReadMe.txt</ code > that is automatically generated from
768- < code > Docs/ ReadMe-portable.txt</ code > .
775+ < code > Docs\ ReadMe-portable.txt</ code > .
769776</ p >
770777
771778< p >
@@ -855,6 +862,31 @@ <h3>
855862 zip file names can be used here too.
856863</ p >
857864
865+ < p >
866+ There is also a quicker way to build a release, but you must provide a version number to use it. First navigate up
867+ to the repository root. Then run
868+ </ p >
869+
870+ < pre class ="cmd "> < span class ="prompt "> ></ span > Deploy 9.9.9</ pre >
871+
872+ < p >
873+ where < code > 9.9.9</ code > is the release version number.
874+ </ p >
875+
876+ < p >
877+ This command will build both the standard and portable executables, the help file, the standard edition setup file
878+ and finally create the release zip files for both editions, with the release version number incorporated in the file names.
879+ </ p >
880+
881+ < p >
882+ Using < code > Deploy 9.9.9</ code > is the equivalent of doing:
883+ </ p >
884+
885+ < pre class ="cmd "> < span class ="prompt "> ></ span > cd Src
886+ < span class ="prompt "> ></ span > Make -DVERSION=9.9.9
887+ < span class ="prompt "> ></ span > Make -DPORTABLE -DVERSION=9.9.9
888+ < span class ="prompt "> ></ span > cd ..</ pre >
889+
858890< h3 >
859891 Clean Up
860892</ h3 >
0 commit comments