summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLloyd Hilaiel <lloyd@hilaiel.com>2010-10-12 09:55:16 -0600
committerLloyd Hilaiel <lloyd@hilaiel.com>2010-10-12 09:55:16 -0600
commitfa8d253822661f7c5ba3bd72a4a4f8fbf2d9bb26 (patch)
tree587b6e4354373264a37c3c69bf40b0c26fc72339
parent5d8b63efe470a724194d860fc427a55555ae878f (diff)
downloadyajl-fa8d253822661f7c5ba3bd72a4a4f8fbf2d9bb26.tar.gz
win32 build documentation improvements (I know, that's subjective. But it's hard to do any worse than lloyd did)
-rw-r--r--BUILDING.win3218
1 files changed, 10 insertions, 8 deletions
diff --git a/BUILDING.win32 b/BUILDING.win32
index 43c3539..6b35aa4 100644
--- a/BUILDING.win32
+++ b/BUILDING.win32
@@ -1,6 +1,7 @@
-YAJL has been successfully built using Visual Studio 8. CMake, a build file
-generator, is used to build the software. CMake provides different build-file
-generators, so you may either build using the IDE via the following steps:
+YAJL has been successfully built using Visual Studio 8. CMake, a
+build file generator, is used to build the software. CMake supports
+several different build environments, so you may either build YAJL
+using the IDE via the following steps:
1. acquire cmake (http://www.cmake.org)
2. mkdir build
@@ -11,9 +12,10 @@ generators, so you may either build using the IDE via the following steps:
Or you can build from the command line using nmake:
-1. Click Start > Programs > Microsoft Visual Studio > Visual Studio Tools > Visual Studio Command Prompt
-for your version of Visual Studio, which will open a command prompt. You may verify that the compiler
-is in your path by typing "cl /?" at the prompt.
+1. Click Start > Programs > Microsoft Visual Studio > Visual Studio
+Tools > Visual Studio Command Prompt -- for your version of Visual
+Studio, which will open a command prompt. You may verify that the
+compiler is in your path by typing "cl /?" at the prompt.
2. cd C:\path\to\yajl\source\
3. mkdir build
4. cd build
@@ -21,5 +23,5 @@ is in your path by typing "cl /?" at the prompt.
6. nmake
7. nmake install
-Earlier versions of visual studio have not been tested, but should
-work without any major issues.
+Earlier versions of visual studio and other build generators haven't
+been thoroughly tested, but should work without any major issues.