Differences

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

--- arma2:tools:makepbo [2017/02/28 07:06] – fixed mikero tools homepage link to a new domain. snakeman
+++ arma2:tools:makepbo [2024/08/02 11:29] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
-====== MakePbo ======
+====== ArmA 2 MakePbo ======
+[[https://www.pmctactical.org/forum/viewforum.php?f=50|ArmA 2 Forum]], [[:arma2|ArmA 2 Home]], [[arma2:config|ArmA 2 Config]], [[arma2:file_formats|ArmA 2 File Formats]], [[arma2:missions|ArmA 2 Missions]], [[arma2:modeling|ArmA 2 3D Modeling]], [[arma2:scripting|ArmA 2 Scripting]], [[arma2:terrain|ArmA 2 Terrain]], [[arma2:texturing|ArmA 2 Texturing]], [[arma2:tools|ArmA 2 Tools]]
 This pbo maker will create one of four different types of pbo depending on options specified on the command line.
@@ Line 22: / Line 24: @@
 -F ignore any #include \hard folders (LintCheck only)
--B Binarise (rapify) any of the above files (except desc.ext)
+-B Binarize (rapify) any of the above files (except desc.ext)
--T binarise  and include config.cpp as config.cpp.txt (eg)
+-T binarize  and include config.cpp as config.cpp.txt (eg)
 -N do Nothing special. Make a pbo wysiwig
@@ Line 41: / Line 43: @@
 </code>
-Note that in the case of desc.ext and bisurfs, they are checked for accuracy only. They are not, 'binarised'
+Note that in the case of desc.ext and bisurfs, they are checked for accuracy only. They are not, 'binarized'
 Note that if a $PBOPREFIX$ file is detected in the pbo folder. It takes precedence. It is a method by which drag and drop applications can create prefix pbo headers, without further intervention. The content of this file, becomes the prefix header, unconditionally. It is also recorded in the pbo for reference.
@@ Line 80: / Line 82: @@
 Requires DePbo.dll - Check [[http://dev.withsix.com/projects/mikero-pbodll/files|Mikero tools homepage]] in Dev-Heaven.