0024944: New custom-built Tcl is source of distribution problems

Option to link to MS run-time library statically added in description of building of Tcl/Tk from sources

Spelling corrections

Order of sections corrected in "Debug tools and hints"

diff --git a/dox/dev_guides/building/3rdparty/3rdparty_windows.md b/dox/dev_guides/building/3rdparty/3rdparty_windows.md
index 48db2701b79044f827cc908db237276b04d0965f..2148d2c6df639bb14478face2506e3909ecf59f1 100644 (file)
--- a/dox/dev_guides/building/3rdparty/3rdparty_windows.md
+++ b/dox/dev_guides/building/3rdparty/3rdparty_windows.md
@@ -63,11 +63,21 @@ Download the necessary archive from http://www.tcl.tk/software/tcltk/download.ht
 
    This is to avoid extra prefix 't' in the library name, which is not recognized by default by OCCT build tools.
 
-3. In the command prompt, run *buildall.vc.bat*
+
+3. By default, Tcl uses dynamic version of run-time library (MSVCRT), which must be installed on the system where Tcl will be used.
+   You may wish to link Tcl library with static version of run-time to avoid this dependency.
+   For that:
+
+   * Edit file *makefile.vc* replacing strings "crt = -MD" by "crt = -MT"
+
+   * Edit source file *tclMain.c* (located in folder *generic*) commenting out forward declaration of function *isatty()*.
+
+
+4. In the command prompt, run *buildall.vc.bat*
 
    You might need to run this script twice to have *tclsh* executable installed; check subfolder *bin* of specified installation path to verify this.
 
-4. For convenience of use, we recommend making a copy of *tclsh* executable created in subfolder *bin* of *INSTALLDIR* and named with Tcl version number suffix, as *tclsh.exe* (with no suffix)
+5. For convenience of use, we recommend making a copy of *tclsh* executable created in subfolder *bin* of *INSTALLDIR* and named with Tcl version number suffix, as *tclsh.exe* (with no suffix)
 
        > cd D:\OCCT\3rdparty\tcltk-86-32\bin
        > cp tclsh86.exe tclsh.exe

diff --git a/dox/dev_guides/debug/debug.md b/dox/dev_guides/debug/debug.md
index 270ee8bdb5bf96f42b7b794e446260dd03dda897..ceed13b10ca66597a97fe5f2d68872d8a0409455 100644 (file)
--- a/dox/dev_guides/debug/debug.md
+++ b/dox/dev_guides/debug/debug.md
@@ -3,6 +3,10 @@ Debugging tools and hints {#occt_dev_guides__debug}
 
 @tableofcontents
 
+@section occt_debug_intro Introduction
+
+This manual describes facilities included in OCCT to support debugging, and provides some hints for more efficient debug.
+
 @section occt_debug_macro Compiler macro to enable extended debug messages
 
 Many OCCT algorithms can produce extended debug messages, usually printed to cout.
@@ -23,10 +27,6 @@ Note that some header files are modified when *OCCT_DEBUG* is enabled, hence bin
 
 On Windows platform when using Visual Studio compiler there is a possibility to start the debugger automatically if an exception is caught in a program running OCCT. For this, set environment variable *CSF_DEBUG* to any value. Note that this feature works only if you enable OCCT exception handler in your application by calling *OSD::SetSignal()*.
 
-@section occt_debug_intro Introduction
-
-This manual describes facilities included in OCCT to support debugging, and provides some hints for more efficient debug.
-
 @section occt_debug_bop Self-diagnostics in Boolean operations algorithm
 
 In real-world applications modeling operations are often performed in a long sequence, while the user sees only the final result of the whole sequence. If the final result is wrong, the first debug step is to identify the offending operation to be debugged further. Boolean operation algorithm in OCCT provides a self-diagnostic feature which can help to do that step.