Add x86_mscoff and x86_omf to platform-specs (#30)

Author: shoo

views/package_format_json.dt

@@ -219,15 +219,17 @@ block body
 
 	p Build settings influence the command line options passed to the compiler and linker. All settings are optional.
 
-	p Platform specific settings are supported through the use of field name suffixes. Suffixes are dash separated list of operating system/architecture/compiler identifiers, as defined in the <a href="http://dlang.org/version.html#PredefinedVersions">D language reference</a>, but converted to lower case. The order of these suffixes is <code>os-architecture-compiler</code>, where any of these parts can be left off. Examples:
+	p Platform specific settings are supported through the use of field name suffixes. Suffixes are dash separated list of operating system/architecture/compiler identifiers, as defined in the <a href="http://dlang.org/version.html#PredefinedVersions">D language reference</a>, but converted to lower case. The order of these suffixes is <code>os-architecture-compiler</code>, where any of these parts can be left off. Additionally on Windows the architectures <code>x86_omf</code> and <code>x86_mscoff</code> can be used with dmd to differentiate between 32 bit object formats used with the <code>--arch</code> switch. Examples:
 
 	pre.code
 		|{
 		|	"versions": ["PrintfDebugging"],
 		|	"dflags-dmd": ["-vtls"],
 		|	"versions-x86_64": ["UseAmd64Impl"]
 		|	"libs-posix": ["ssl", "crypto"],
-		|	"sourceFiles-windows-x86_64-dmd": ["lib/win32/mylib.lib"],
+		|	"sourceFiles-windows-x86_64-dmd": ["libs/windows-x86_64/mylib.lib"],
+		|	"sourceFiles-windows-x86_omf-dmd": ["libs/windows-x86_omf/mylib.lib"],
+		|	"sourceFiles-windows-x86_mscoff-dmd": ["libs/windows-x86_mscoff/mylib.lib"],
 		|}
 
 	table

views/package_format_sdl.dt

@@ -346,7 +346,7 @@ block body
 
 	h3#platform-specs Platform specifications
 
-	p Platform specific settings are supported through the use of the "platform" attribute. Platform attributes contain dash separated list of operating system/architecture/compiler identifiers, as defined in the <a href="http://dlang.org/version.html#PredefinedVersions">D language reference</a>, but converted to lower case. The order of these suffixes is <code>os-architecture-compiler</code>, where any of these parts can be left off. Examples:
+	p Platform specific settings are supported through the use of the "platform" attribute. Platform attributes contain dash separated list of operating system/architecture/compiler identifiers, as defined in the <a href="http://dlang.org/version.html#PredefinedVersions">D language reference</a>, but converted to lower case. The order of these suffixes is <code>os-architecture-compiler</code>, where any of these parts can be left off. Additionally on Windows the architectures <code>x86_omf</code> and <code>x86_mscoff</code> can be used with dmd to differentiate between 32 bit object formats used with the <code>--arch</code> switch. Examples:
 
 	pre.code
 		|// used on all platforms
@@ -358,7 +358,9 @@ block body
 		|// only used on Posix systems (Linux, OS X, FreeBSD etc.)
 		|libs "ssl" "crypto" platform="posix"
 		|// applies if compiled for Windows, X86-64 using DMD
-		|sourceFiles "lib/win32/mylib.lib" platform="windows-x86_64-dmd"
+		|sourceFiles "lib/windows-x86_64/mylib.lib" platform="windows-x86_64-dmd"
+		|sourceFiles "lib/windows-x86_omf/mylib.lib" platform="windows-x86_omf-dmd"
+		|sourceFiles "lib/windows-x86_mscoff/mylib.lib" platform="windows-x86_mscoff-dmd"
 
 
 	h3#version-specs Version specifications