Getting Started: Difference between revisions

Line 16:

* Now start razzle: <code>tools\razzle.cmd free offline</code> for 32-bit clients, and <code>tools\razzle64.cmd free offline</code> for 64-bits. This initiates retail build of x86. The first time you run razzle inside that copy of the source code it'll need to initialize a few things, give it a few minutes, after a while a Notepad window will appear - make sure to close this for the initialization to continue.

* '''Important for first time!''' Run the prebuild script, if you're initiating source code for first time: <code>tools\prebuild</code>. This scripts sets all read-only attributes for necessary stuff and makes 16-bit stuff workable for x64 environments.

* Start to build via <code>build /cZP</code> or <code>bcz</code> (which is alias to first, so doesn't matter). '''Important:''' Build.exe doesn't seem to play well when building with many (~~over 4~~) threads. If your build machine has more than that it's recommended to cap it to 4 threads maximum via the <code>-M 4</code> switch, added to the build command (eg. <code>build /cZP -M 4</code>, or <code>bcz -M 4</code>)

* Start to build via <code>build /cZP</code> or <code>bcz</code> (which is alias to first, so doesn't matter). '''Important:''' Build.exe doesn't seem to play well when building with many (up to 8) threads. If your build machine has more than that it's recommended to cap it to 8 threads maximum via the <code>-M 8</code> switch, added to the build command (eg. <code>build /cZP -M 8</code>, or <code>bcz -M 8</code>). Use 8 threads if your host/virtual machine CPU have allocated 8 cores (or less). More than 8 threads build may lead to unforeseen behavior, such as inconsistent linkage and invalid generation of pieces of code, since some build programs were written back at time when CPUs should be limited in order to preserve proper frequency.

=== Post-build ===

@@ Line 16: / Line 16: @@
 * Now start razzle: <code>tools\razzle.cmd free offline</code> for 32-bit clients, and <code>tools\razzle64.cmd free offline</code> for 64-bits. This initiates retail build of x86. The first time you run razzle inside that copy of the source code it'll need to initialize a few things, give it a few minutes, after a while a Notepad window will appear - make sure to close this for the initialization to continue.
 * '''Important for first time!''' Run the prebuild script, if you're initiating source code for first time: <code>tools\prebuild</code>. This scripts sets all read-only attributes for necessary stuff and makes 16-bit stuff workable for x64 environments.
-* Start to build via <code>build /cZP</code> or <code>bcz</code> (which is alias to first, so doesn't matter). '''Important:''' Build.exe doesn't seem to play well when building with many (over 4) threads. If your build machine has more than that it's recommended to cap it to 4 threads maximum via the <code>-M 4</code> switch, added to the build command (eg. <code>build /cZP -M 4</code>, or <code>bcz -M 4</code>)
+* Start to build via <code>build /cZP</code> or <code>bcz</code> (which is alias to first, so doesn't matter). '''Important:''' Build.exe doesn't seem to play well when building with many (up to 8) threads. If your build machine has more than that it's recommended to cap it to 8 threads maximum via the <code>-M 8</code> switch, added to the build command (eg. <code>build /cZP -M 8</code>, or <code>bcz -M 8</code>). Use 8 threads if your host/virtual machine CPU have allocated 8 cores (or less). More than 8 threads build may lead to unforeseen behavior, such as inconsistent linkage and invalid generation of pieces of code, since some build programs were written back at time when CPUs should be limited in order to preserve proper frequency.
 === Post-build ===