* docs/DEBUG: Update documentation.

2 files changed, 16 insertions, 2 deletions

diff --git a/[priyesh]ChangeLog b/[priyesh]ChangeLog
index 23fc7047d..328ffd63d 100644
--- a/[priyesh]ChangeLog
+++ b/[priyesh]ChangeLog
@@ -1,5 +1,7 @@
 2020-08-24  Priyesh Kumar  <priyeshkkumar@gmail.com>
 
+    * docs/DEBUG: Update documentation.
+
     * builds/windows/ftdebug.c (ft_logging_init, ft_logging_init):
     Fixed coding style. 
 
diff --git a/docs/DEBUG b/docs/DEBUG
index 49365ba65..a1af0c627 100644
--- a/docs/DEBUG
+++ b/docs/DEBUG
@@ -42,8 +42,9 @@ located in the file `ftoption.h'.  The macros are:
     Now,  `FT_TRACE'  and  `FT_ERROR'  macros  will start  sending the
     tracing  and  debugging   messages  to  the file system instead of
     `stderr'.
-    On the file system the log file  with name `freetype2.log' will be
-    generated in the same directory where the executable is placed.  
+    On  the  file system  the  log  file will be generated on the path 
+    specified  using  `FT_LOGGING_FILE'  environment  variable(more on
+    this later).
 
     There is an additional support  of  logging  Time and the  name of
     the `FT_COMPONENT' from which the current  log is  generated along
@@ -202,6 +203,17 @@ behaviour of FreeType at runtime.
 
             [{ttload}] table directory loaded
 
+  FT_LOGGING_FILE
+
+    This  variable   is  only  used   when  FreeType  is   built  with
+    `FT_LOGGING' macro defined. It contains the path to the file where
+    the user wants to put his log file.
+
+      On Linux with bash:
+      export FT_LOGGING_FILE="/tmp/freetype2.log"      
+
+      On Windows:
+      set FT_LOGGING_FILE=C:\Users\AppData\Local\Temp\freetype2.log
 
   FT2_DEBUG_MEMORY