summaryrefslogtreecommitdiff
path: root/Tools/freeze/checkextensions_win32.py
diff options
context:
space:
mode:
Diffstat (limited to 'Tools/freeze/checkextensions_win32.py')
-rw-r--r--Tools/freeze/checkextensions_win32.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/Tools/freeze/checkextensions_win32.py b/Tools/freeze/checkextensions_win32.py
index a41542f20e..ee446e754a 100644
--- a/Tools/freeze/checkextensions_win32.py
+++ b/Tools/freeze/checkextensions_win32.py
@@ -3,7 +3,7 @@
Under Windows it is unlikely the .obj files are of use, as special compiler options
are needed (primarily to toggle the behavior of "public" symbols.
-I dont consider it worth parsing the MSVC makefiles for compiler options. Even if
+I don't consider it worth parsing the MSVC makefiles for compiler options. Even if
we get it just right, a specific freeze application may have specific compiler
options anyway (eg, to enable or disable specific functionality)
@@ -14,7 +14,7 @@ So my basic strategy is:
your own).
* This description can include:
- The MSVC .dsp file for the extension. The .c source file names
- are extraced from there.
+ are extracted from there.
- Specific compiler/linker options
- Flag to indicate if Unicode compilation is expected.