That behaviour is caused by this 3 commands:
#command ? => outstd(EOL)
#command ? <xx,...> => outstd(EOL);outstd(<xx>)
#command ?? <xx,...> => outstd(<xx>)
qout() sends output to console window
outstd() sends output to standar program output, and you only use this
if you want to write a cgi program.
So in alaska's dialect console <> stdout
HTH
Angel
Viktor Szakáts escribió:
Hi Angel,
You need to update your environment, it's difficult to follow
what's happening exactly.
I've been posting ready-to-use sample make scripts to this
list (last time yesterday), there is an extensive INSTALL doc
for details, and you may also download pre-built installer or
.zip for MSVC 2008 (posted a few days ago).
compile.bat
-----------------------------------------------------------------
SET PATH=C:\vsk\vc\bin;C:\vsk\bin;C:\harbour\bin;
SET LIB=C:\vsk\vc\lib;C:\vsk\lib;C:\harbour\lib\win\msvc;
SET INCLUDE=C:\vsk\vc\include;C:\vsk\include;C:\harbour\include;
set HB_VISUALC_VER=90
hbmk2.exe speedtst.prg -shared -mt -gc3
-----------------------------------------------------------------
Problem:
in C:\harbour\bin there's a february version of harbour and hbmk2
New exe ares in C:\harbour\bin\vc
Normally they shouldn't be there, this is old non-GNU
target area, no longer used.
HB_VISUALC_VER=90 is also no longer used and needed.
So I changed my bat line to:
SET PATH=C:\vsk\vc\bin;C:\vsk\bin;C:\harbour\bin\vc;
and then hbmk2.exe bombs out with this message:
hbmk: Error: Running harbour compiler. 1:
C:\harbour\bin\bin\harbour.exe speedtst.prg -iC:\harbour\bin\include
^^^
hbmk2 expects to be run from bin dir directly. bin/vc which
also contains harbour.exe will confuse it, but such layout
isn't possible when using current build tools.
I'd suggest to you to start over with a fresh source dir, then
using the build sample script posted yesterday (or any other
option from above).
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
