Initial Commit

Author: jonathanpepinmoore

docs/building/interix.html

@@ -52,7 +52,28 @@ <h2>Interix</h2>
 
 <p>Please read the INSTALL file of each project for full directions.</p>
 
-<p><a href="https://www.prnewswire.com/news-releases/xinuos-sues-ibm-and-red-hat-for-antitrust-violations-and-copyright-infringement-alleges-ibm-has-been-misleading-its-investors-since-2008-301259756.html">Xinuos Sues IBM and Red Hat for Antitrust Violations and Copyright Infringement</a></p>
+<p>
+Building FreeBSD on Cygwin
+involves cross-compiling, as Cygwin acts as a POSIX emulation layer on Windows, not a native BSD environment. This requires configuring the build toolchain, using make.py or standard make with target architecture flags (TARGET/TARGET_ARCH), and ensuring necessary developer tools are installed within Cygwin. 
+Key Steps for Building FreeBSD on Cygwin:
+
+    Prepare Environment: Install Cygwin with essential build tools: git, make, gcc-core, gcc-g++, binutils, and python3.
+    Obtain Source: Clone the FreeBSD source repository (e.g., stable/14) using Git.
+    Cross-Build Structure: Use tools/build/make.py or set TARGET (e.g., amd64) and TARGET_ARCH (e.g., amd64) environment variables.
+    Toolchain: Utilize the in-tree LLVM/Clang by passing --bootstrap-toolchain to tools/build/make.py for a more reliable build compared to external GCC.
+    Build Process: Run make buildworld and make buildkernel within the Cygwin terminal. 
+
+Important Considerations:
+
+    Performance: Building on Cygwin can be slower than native FreeBSD.
+    Alternatives: Using a virtual machine running FreeBSD directly is generally recommended for building FreeBSD to avoid compatibility issues.
+    Toolchains: While you can use external GCC, it is often more complex, requiring specific cross-toolchain setup. 
+
+For detailed steps, referring to the BuildingOnNonFreeBSD wiki is crucial
+</p>
+
+<pre>export XCC=x86_64-w64-mingw32 XCXX=x86_64-w64-mingw32 XCPP=x86_64-w64-mingw32 XLD=x86_64-w64-mingw32
+MAKEOBJDIRPREFIX=/usr/obj ./tools/build/make.py --cross-toolchain=gcc-core -DWITH_FOO TARGET=amd64 TARGET_ARCH=amd64</pre>
 
 <p><a href="https://www.opengroup.org/openbrand/register/">Registered UNIX Products</a></p>
 
@@ -90,25 +111,10 @@ <h2>Interix</h2>
 
 <p>You should always use the Administrator account and fill out your Full Name</p>
 
-<pre>
-Building FreeBSD on Cygwin
-involves cross-compiling, as Cygwin acts as a POSIX emulation layer on Windows, not a native BSD environment. This requires configuring the build toolchain, using make.py or standard make with target architecture flags (TARGET/TARGET_ARCH), and ensuring necessary developer tools are installed within Cygwin. 
-Key Steps for Building FreeBSD on Cygwin:
-
-    Prepare Environment: Install Cygwin with essential build tools: git, make, gcc-core, gcc-g++, binutils, and python3.
-    Obtain Source: Clone the FreeBSD source repository (e.g., stable/14) using Git.
-    Cross-Build Structure: Use tools/build/make.py or set TARGET (e.g., amd64) and TARGET_ARCH (e.g., amd64) environment variables.
-    Toolchain: Utilize the in-tree LLVM/Clang by passing --bootstrap-toolchain to tools/build/make.py for a more reliable build compared to external GCC.
-    Build Process: Run make buildworld and make buildkernel within the Cygwin terminal. 
-
-Important Considerations:
+<p><a href="https://www.prnewswire.com/news-releases/xinuos-sues-ibm-and-red-hat-for-antitrust-violations-and-copyright-infringement-alleges-ibm-has-been-misleading-its-investors-since-2008-301259756.html">Xinuos Sues IBM and Red Hat for Antitrust Violations and Copyright Infringement</a></p>
 
-    Performance: Building on Cygwin can be slower than native FreeBSD.
-    Alternatives: Using a virtual machine running FreeBSD directly is generally recommended for building FreeBSD to avoid compatibility issues.
-    Toolchains: While you can use external GCC, it is often more complex, requiring specific cross-toolchain setup. 
 
-For detailed steps, referring to the BuildingOnNonFreeBSD wiki is crucial
-</pre>								</section>
+								</section>
 							</div>
 						</div>
 					</div>