Hi Manoj,
here is some explanation of the \hmg\build.bat
which is used for compilation.
The reason, why older HMG-Releases will compile Console-Mode
without altering BUILD.BAT
Build.bat ---- GUI Mode
rem *******************************************************************************
rem SET DEFAULT OPTIONS
rem *******************************************************************************
set gtdrivers=-gtgui -gtwin
set runafterbuild=.t.
set debug=
//----------------------------------------
Build.Bat ---- Mixed Mode
rem *******************************************************************************
rem SET DEFAULT OPTIONS
rem *******************************************************************************
set gtdrivers=-gtwin -gtstd
set runafterbuild=.t.
set debug=
//-----------------------------------------------
Build.Bat ---- suppose this is pure Console Mode startup routines for windows
rem *******************************************************************************
rem SET DEFAULT OPTIONS
rem *******************************************************************************
set gtdrivers=-gtstd
set runafterbuild=.t.
set debug=
//---------------------------
The driver libs are in hmg.3.1.x\
harbour\lib\win\mingw\libgtwin.a
hmg.3.1.x\
harbour\lib\win\mingw\libgtstd.a
....
all these libgt***.a have terminal capabillities
even libgtalleg.a as it opens a terminal for
special handling.
In former
Harbour(!) versions there was gtdos.a (GCC) or gtdos.lib (Watcom) for the handling
of DOS-Based screen operations.
So simply keep in mind, that the newer HMG-Versions not explicitly
support Console-Mode in Windows.
But with -gtstd it is possible to use Windows-Console-Mode Operation, if -GTGUI is omitted.
So it is up to you, to use
Harbour in Console-Mode or HMG in -GTSTD Mode
for your Clipper-Application to test.
As much as I have tested, the -GTGUI is preventing -GTSTD - Mode.
So you have to play somewhat until things fit your purpose.
Happy HMG'ing
Greetings from Germany
klauskugel