Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
install:nix [2019/09/04 11:34] – clarify location to run cleanall.sh daitenguinstall:nix [2020/01/10 17:44] – [Clean Rebuild] typo digital man
Line 45: Line 45:
   * Note: these commands will make and install a //RELEASE// build of the software. To make and install a //DEBUG// build instead, pass ''DEBUG=1'' on the ''make'' command-lines.   * Note: these commands will make and install a //RELEASE// build of the software. To make and install a //DEBUG// build instead, pass ''DEBUG=1'' on the ''make'' command-lines.
   * Note: if you installed with a specified ''CVSTAG'' value and wish to reset this "sticky tag" later (i.e. to get the latest and greatest files from CVS), execute ''cvs update -A -d'' from the installation directory and rebuild.   * Note: if you installed with a specified ''CVSTAG'' value and wish to reset this "sticky tag" later (i.e. to get the latest and greatest files from CVS), execute ''cvs update -A -d'' from the installation directory and rebuild.
 +  * Note: due to files being moved in CVS between releases, the **CVSTAG=xxx** method of specifying a specific source release version may not always work. Get/extract the relevant tarball for the desired release (e.g. ''ssrc317b.zip'') instead, as detailed in the next section.
 ==== Non-CVS ==== ==== Non-CVS ====
 Alternatively, if you don't have a working CVS client, you can use the following steps to install the latest nightly development build: Alternatively, if you don't have a working CVS client, you can use the following steps to install the latest nightly development build:
Line 308: Line 309:
  
 **Note**:\\ **Note**:\\
-If you elect to build //debug// binaries (instead of //release// binaries), then you'll need to //exclude// the ''RELEASE=1'' portion from the ''cleanall.sh'' command. Otherwise, you'll be cleaning the ''*.release'' output directories when you really need to be cleaning the ''*.debug'' output directories. Likewise, if you're building and running //release// binaries, then you need to //include// the ''RELEASE=1'' portion on the ''cleanall.sh'' commandsas well. Alternatively, you can set your default build type in the file ''localdefs.mk''. The ''localdefs.mk'' file should be created by you in either in the ''src/build'' directory (to apply to //all// builds), or within each directory you run ''make'':+If you elect to build //debug// binaries (instead of //release// binaries), then you'll need to //exclude// the ''RELEASE=1'' portion from the ''cleanall.sh'' command. Otherwise, you'll be cleaning the ''*.release'' output directories when you really need to be cleaning the ''*.debug'' output directories. Likewise, if you're building and running //release// binaries, then you need to //include// the ''RELEASE=1'' portion on the ''cleanall.sh'' commands as well. Alternatively, you can set your default build type in the file ''localdefs.mk''. The ''localdefs.mk'' file should be created by you in either in the ''src/build'' directory (to apply to //all// builds), or within each directory you run ''make'':
   RELEASE=1   RELEASE=1