[Harbour] RE: make system GNU and non-GNU

[Rodrigo Miguel]

Hi Massimo,

> Where I put files extracted from
> http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=23918
?

You can put in any place that you want, just add that to the PATH variable.

Attached, you will find one good sample that compile all files inside of a
src folder, so create those files and place the Makefile in the root:

src
bin
obj

Regards
Rodrigo


Makefile
Description: Binary data
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] Mouse not work with ACHOICE()

[Guillermo Varona Silupú]

Hello, I've verified that also works in xHarbour the mouse.
Can we fix this in harbour?

Best Regards
GVS

P.D.: Sorry for my bad english.

Guillermo Varona Silupú escribió:

This Code work fine in clipper with the mouse:

#include "inkey.ch"// Key definitions
FUNCTION MAIN
  LOCAL aOpc := {"Opc. 1","Opc. 2","Opc. 3"}, nOpc
  SET( _SET_EVENTMASK, INKEY_ALL )
  cls
  nOpc := ACHOICE(1,1,10,20,aOpc)
  ? nOpc
  RETURN NIL

In harbour not work the mouse.

Best Regards.
GVS
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


__ Information from ESET Smart Security, version of virus 
signature database 3317 (20080801) __


The message was checked by ESET Smart Security.

http://www.eset.com





___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] 2008-08-05 23:47 UTC+0200 Viktor Szakats (harbour.01 syenar hu)

[Szakáts Viktor]

2008-08-05 23:47 UTC+0200 Viktor Szakats (harbour.01 syenar hu)
   * source/rtl/errorint.c
   * source/vm/estack.c
   * source/vm/hvm.c
   * source/vm/extrap.c
 + Added filename to stack traces. Someone please review me.
   Also, pls test if it compiles cleanly with OS/2.
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] 2008-08-05 21:39 UTC+0200 Viktor Szakats (harbour.01 syenar hu)

[Szakáts Viktor]

2008-08-05 21:39 UTC+0200 Viktor Szakats (harbour.01 syenar hu)
   * source/hbpcre/_hbconf.h
   * source/hbzlib/zconf.h
   * source/hbzlib/ChangeLog
 ! Fixed to pass down Harbour DLL creation flag to 
   integrated 3rd party sources.
   After this, pcre and zlib public symbols should be 
   properly exported on Windows platform.
 ; NOTE: Harbour uses __EXPORT__ to signal DLL creation, 
 which is not very ideal, so I'd suggest to 
 switch to HB_DLL in future versions.
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

RE: [Harbour] re: make system GNU and non-GNU

[Massimo Belgrano]

Hi Rodrigo
Thanks for info . I use typically bcc,win32
Can you help me about How start gnu make system in mingw?
Where I put files extracted from
http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=23
918 ?


regards

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rodrigo Miguel
Sent: Tuesday, August 05, 2008 8:02 PM
To: Harbour Project Main Developer List.
Subject: [Harbour] re: make system GNU and non-GNU

HI Massimo,

Why you don't use the gnu make? I use that on regular basis for my apps
even in windows, so I just have one single makefile for linux and
windows.

You can download that from:
http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=23
918

Here you have a complete documentation about it:
http://www.gnu.org/software/make/manual/make.html

Regards
Rodrigo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] re: make system GNU and non-GNU

[Rodrigo Miguel]

HI Massimo,

Why you don't use the gnu make? I use that on regular basis for my apps even
in windows, so I just have one single makefile for linux and windows.

You can download that from:
http://sourceforge.net/project/showfiles.php?group_id=2435&package_id=23918

Here you have a complete documentation about it:
http://www.gnu.org/software/make/manual/make.html

Regards
Rodrigo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek,


I've changed mainstd to hbmainstd, and it worked altough the
result looked quite strange :), after that I've rebuilt it
with -shared, and it gave a 'compress2' missing entry.
Which pbly indicates that hbzlib is missing from harbour.dll
in non-GNU make.


It should be added just like hbpcre it it's also missing.


I've checked and they are added, so the problem
seems to be that the public zlib, pcre interface
is not marked as HB_EXPORT (or export by any
other means).


After this I reduced hbrun.prg to a pure 4 lines long program
displaying hb_compiler() and waiting for a key. Then it told
's_defaultGT', and at this point I'm pretty much lost.


This I'll try to resolve tomorrow. I'll replace it with function
call. I do not know if I will have inet access in the evening.


Thanks, take your time, not having internet is
actually a very good opportunity to
worry about it^^^to talk to ppl,
read some books, or go out or something :)

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Lorenzo,


I've changed C: to /c/ everywhere except the PATH.
[ but it didn't fix the sed problem. ]


The sed you should use is the one inside msys which is in c:\msys 
\1.0\bin.


Mixing msys and non-msys tools is the main source of problems.
msys is a posix env and it means the c:\bin\harbour.exe is read like
c:binharbour.exe.
If you want the right path you need to enter c:\\bin\\harbour.exe or
better /bin/harbour.exe


This is what I use, at least almost, since I don't know
of any place where I should specify the location of harbour.exe,
the dir specs I'm using are fully /c/bin/... formatted (can't
use /bin, not wanting to trash in the root).

I have tried to reverse my PATH to first include msys, and
mingw afterwards. This blew the whole build process, creating
an infinite loop, an unstoppable chain of sh.exe crashes
and launches, and an unusable system, with no way to pull up
Task Manager. I managed to kill make/sh by issuing a pskill
for both at the same time (killing about 1500 instances of them).
(so don't anybody try this at home.)

Finally I simply copied over sed.exe from msys to mingw dir,
and this way it worked without the error. Thanks for the tip.

[ I wonder however how these tools are meant to be used properly,
if even a 'sed' cannot work consistently along different builds,
not to mention the rest of the mess. I also wonder if there is
any clean method achieve the above effect. ]

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Lorenzo Fiorini]

On Tue, Aug 5, 2008 at 5:53 PM, Szakáts Viktor <[EMAIL PROTECTED]> wrote:

> I've changed C: to /c/ everywhere except the PATH.
> [ but it didn't fix the sed problem. ]

The sed you should use is the one inside msys which is in c:\msys\1.0\bin.

Mixing msys and non-msys tools is the main source of problems.
msys is a posix env and it means the c:\bin\harbour.exe is read like
c:binharbour.exe.
If you want the right path you need to enter c:\\bin\\harbour.exe or
better /bin/harbour.exe

best regards,
Lorenzo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> >MAJOR=`sed -e '!HB_VER_MAJOR!!d' -e 's![^0-9]*\([^ ]*\).*!\1!g'  
> >"${FVER}"`
> >MINOR=`sed -e '!HB_VER_MINOR!!d' -e 's![^0-9]*\([^ ]*\).*!\1!g'  
> >"${FVER}"`
> >REVIS=`sed -e '!HB_VER_REVISION! !d' -e 's![^0-9]*\([^ ]*\).*!\1!g'  
> >"${FVER}"`
> 
> With this one it says:
> '-e expression #1, char 3: extra characters after command'

Please try to use other unique character, f.e.: '@'. I missed that I use !d.
Tomorrow I'll try to setup MinGW/MSYS environment in one of MW-Win machine
in my firm and make some tests too.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> Well, there is no "WinMain" at all in harbour-vc.dlls, but
> there is one '?DllEntryPoint@@' in C++, and a
> '[EMAIL PROTECTED]' in C.

As workaround I can add WinMain() or main() dynamically in hb* scripts
and add -gui switch for windows users to control the version.

> >Please also try to make console application by adding to hbmk - 
> >lmainstd
> >switch, f.e.:
> >  hbmk -n -w -es2 -lmainstd -gtstd hbrun
> I've changed mainstd to hbmainstd, and it worked altough the
> result looked quite strange :), after that I've rebuilt it
> with -shared, and it gave a 'compress2' missing entry.
> Which pbly indicates that hbzlib is missing from harbour.dll
> in non-GNU make.

It should be added just like hbpcre it it's also missing.

> After this I reduced hbrun.prg to a pure 4 lines long program
> displaying hb_compiler() and waiting for a key. Then it told
> 's_defaultGT', and at this point I'm pretty much lost.

This I'll try to resolve tomorrow. I'll replace it with function
call. I do not know if I will have inet access in the evening.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek,

MAJOR=`sed -e '/HB_VER_MAJOR/!d' -e 's/[^0-9]*\([^ ]*\).*/\1/ 
g'<"${FVER}"`
MINOR=`sed -e '/HB_VER_MINOR/!d' -e 's/[^0-9]*\([^ ]*\).*/\1/ 
g'<"${FVER}"`
REVIS=`sed -e '/HB_VER_REVISION/ !d' -e 's/[^0-9]*\([^ ]*\).*/\1/ 
g'<"${FVER}"`


This didn't change the results.

MAJOR=`sed -e '!HB_VER_MAJOR!!d' -e 's![^0-9]*\([^ ]*\).*!\1!g'  
"${FVER}"`
MINOR=`sed -e '!HB_VER_MINOR!!d' -e 's![^0-9]*\([^ ]*\).*!\1!g'  
"${FVER}"`
REVIS=`sed -e '!HB_VER_REVISION! !d' -e 's![^0-9]*\([^ ]*\).*!\1!g'  
"${FVER}"`


With this one it says:
'-e expression #1, char 3: extra characters after command'

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek,


So, to give a short list of Windows .dll problems:
- 'sed' command line error.


This is probably caused by the C: prefix in your paths.
Probably if you use /c/ instead then this message will
disappear. I'll try to located it and add some workarounds.


Thanks, I'll update my environment anyways, better be
friendly with msys.

I've changed C: to /c/ everywhere except the PATH.
[ but it didn't fix the sed problem. ]


- harbour*.dll naming in non-GNU make system.
- harbour.dll install location doesn't match in GNU ('lib') and non-
GNU ('bin') builds.


I know about it but I left for user decisions where to put it.
Anyhow if other non GNU Windows make systems store harbour*.dll
in HB_BIN_INSTALL then I can update postinst.sh to make the same.


That would be great. If it's in lib, one has to always fiddle
with either copying it next to the .exe, or to some system dirs,
or to put the lib dir in the path, I personally hate to do any
of these (especially the latter two).


- harbour.dll content doesn't match in GNU and non-GNU (missing
hbcplr) builds.


Yes but probably we should remove hbcplr from commercial builds.
There is still open question about rewriting some part of compiler
which uses pure GPL license with different license similar to Harbour
exception but which will have additional condition: any binaries  
created

from modified version of this code (directly on indirectly by some
macros) has to be distributed with modified source code and build
scripts so each user should be able to replicate exactly the same
version of hbcplr library.
But this is other subject. I'll exclude hbcplr from harbour shared
libraries before final release.


Thanks, I think it is the way to go (excluding the compiler stuff
from harbour.dll).


- harbour.dll generated with BCC isn't compatible with MSVS and MinGW
ones (due to added leading underscore in BCC).


Yes and I do not know if it's possible to make MSVC compatible library
using BCC.


That would be a huge shame on BCC...


- Minor: Generation of harbour.dll using the GNU-make system under
Windows, needs full msys shell support. Maybe it would be better to  
include

this process in the GNU-make system itself (if possible at all).


It rather needs bash only and some GNU/MinGW tools. It can be resolved
when we add alternative version of hb* tools written in .c. Now they
are BASH scripts only.


Isn't it a possibility to somehow integrate the .dll creation
process into the GNU-make system? (rather than having a separate
post-script to do it)

It's not a huge problem to use msys to create MinGW builds though
(once you got through the initial gotchas).

- MinGW generated shared-lib .exe is not compatible with MSVS  
generated

 harbour.dll. (missing '[EMAIL PROTECTED]' entry)


Can you check how this symbol looks in the final MSVC dll?
It probably have some very similar name. It can be different
in pure C and C++ builds.


Well, there is no "WinMain" at all in harbour-vc.dlls, but
there is one '?DllEntryPoint@@' in C++, and a
'[EMAIL PROTECTED]' in C.

Please also try to make console application by adding to hbmk - 
lmainstd

switch, f.e.:
  hbmk -n -w -es2 -lmainstd -gtstd hbrun


I've changed mainstd to hbmainstd, and it worked altough the
result looked quite strange :), after that I've rebuilt it
with -shared, and it gave a 'compress2' missing entry.

Which pbly indicates that hbzlib is missing from harbour.dll
in non-GNU make.

After this I reduced hbrun.prg to a pure 4 lines long program
displaying hb_compiler() and waiting for a key. Then it told
's_defaultGT', and at this point I'm pretty much lost.

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] make system GNU and non-GNU

[Massimo Belgrano]

non-GNU make system seem different, is aivable documentation for etiher?
Is possible write a make system in prg compatible with ether hb-func.sh
and bld.bat?
Can somebody give me a starting point?
Massimo Belgrano

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Przemyslaw Czerpak wrote:

Hi Viktor,
> > So, to give a short list of Windows .dll problems:
> > - 'sed' command line error.
> This is probably caused by the C: prefix in your paths.
> Probably if you use /c/ instead then this message will
> disappear. I'll try to located it and add some workarounds.

Can you make a test and change in bin/hb-fun.sh[48-50]:

 MAJOR=`sed -e '/HB_VER_MAJOR/!d' -e 's/[^0-9]*\([^ ]*\).*/\1/g' "${FVER}"`
 MINOR=`sed -e '/HB_VER_MINOR/!d' -e 's/[^0-9]*\([^ ]*\).*/\1/g' "${FVER}"`
 REVIS=`sed -e '/HB_VER_REVISION/ !d' -e 's/[^0-9]*\([^ ]*\).*/\1/g' "${FVER}"`

to:

 MAJOR=`sed -e '/HB_VER_MAJOR/!d' -e 's/[^0-9]*\([^ ]*\).*/\1/g'<"${FVER}"`
 MINOR=`sed -e '/HB_VER_MINOR/!d' -e 's/[^0-9]*\([^ ]*\).*/\1/g'<"${FVER}"`
 REVIS=`sed -e '/HB_VER_REVISION/ !d' -e 's/[^0-9]*\([^ ]*\).*/\1/g'<"${FVER}"`

Just add '<' before "${FVER}"
In such version "${FVER}" is not passed to sed as parameter but file body
is redirected to sed stdin.
Does it eliminate the problem?
If not then please also test the version where all '/' are replace by '!':

 MAJOR=`sed -e '!HB_VER_MAJOR!!d' -e 's![^0-9]*\([^ ]*\).*!\1!g' "${FVER}"`
 MINOR=`sed -e '!HB_VER_MINOR!!d' -e 's![^0-9]*\([^ ]*\).*!\1!g' "${FVER}"`
 REVIS=`sed -e '!HB_VER_REVISION! !d' -e 's![^0-9]*\([^ ]*\).*!\1!g' "${FVER}"`


best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] Re: [xHarbour-developers] TortoiseCVS

[Alex Strickland]

Hi Patrick


I use Tortoise 1.8.31.  What new version did you install?


1.10.7, although little good it has done me so far. Are you able to
Update from the server? Anonymous access seems ok.

PS. Harbour uses SVN now and it works much faster than CVS. Are we also 
interested in converting from SCV to SVN?


Yes, it is much faster. I had nothing to do with the conversion but
the it seemed quite a lot of work.

Regards
Alex

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> So, to give a short list of Windows .dll problems:
> - 'sed' command line error.

This is probably caused by the C: prefix in your paths.
Probably if you use /c/ instead then this message will
disappear. I'll try to located it and add some workarounds.

> - harbour*.dll naming in non-GNU make system.
> - harbour.dll install location doesn't match in GNU ('lib') and non- 
> GNU ('bin') builds.

I know about it but I left for user decisions where to put it.
Anyhow if other non GNU Windows make systems store harbour*.dll
in HB_BIN_INSTALL then I can update postinst.sh to make the same.

> - harbour.dll content doesn't match in GNU and non-GNU (missing  
> hbcplr) builds.

Yes but probably we should remove hbcplr from commercial builds.
There is still open question about rewriting some part of compiler
which uses pure GPL license with different license similar to Harbour
exception but which will have additional condition: any binaries created
from modified version of this code (directly on indirectly by some
macros) has to be distributed with modified source code and build
scripts so each user should be able to replicate exactly the same
version of hbcplr library.
But this is other subject. I'll exclude hbcplr from harbour shared
libraries before final release.

> - harbour.dll generated with BCC isn't compatible with MSVS and MinGW  
> ones (due to added leading underscore in BCC).

Yes and I do not know if it's possible to make MSVC compatible library
using BCC.

> - Minor: Generation of harbour.dll using the GNU-make system under
> Windows, needs full msys shell support. Maybe it would be better to include
> this process in the GNU-make system itself (if possible at all).

It rather needs bash only and some GNU/MinGW tools. It can be resolved
when we add alternative version of hb* tools written in .c. Now they
are BASH scripts only.

> - MinGW generated shared-lib .exe is not compatible with MSVS generated
>   harbour.dll. (missing '[EMAIL PROTECTED]' entry)

Can you check how this symbol looks in the final MSVC dll?
It probably have some very similar name. It can be different
in pure C and C++ builds.

Please also try to make console application by adding to hbmk -lmainstd
switch, f.e.:
   hbmk -n -w -es2 -lmainstd -gtstd hbrun

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] Including makefile in prg

[Guy Roussin]

Hi,

I wrote only little apps (scripts) with harbour.
Now i put these lines on top of my prg :

-
#ifdef SH_COMPILATION /* sh compilation :
hbmk -n -p -gtcgi -gtstd -gtpca -gttrm -gtxwc -L/usr/lib/mysql -lmysqlclient $0
nameprg="$0"
shift
./${nameprg%.*} "$*"
exit
*/
#endif
--

So i can compile and exec my apps with :
./my.prg myparameters

This is very usefull when i can't put #!/usr/bin/hbrun because all libraries
are not linked with hbrun.

Perhaps there is a more beautifull or generic way to do this ?



Guy
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] 2008-08-05 16:29 UTC+0200 Viktor Szakats (harbour.01 syenar hu)

[Szakáts Viktor]

2008-08-05 16:29 UTC+0200 Viktor Szakats (harbour.01 syenar hu)
   * contrib/examples/pp/bld_b32.bat
   * contrib/examples/pp/bld_vc.bat
   * contrib/examples/guestbk/bld_b32.bat
   * contrib/examples/guestbk/bld_vc.bat
   * contrib/examples/pe/bld_b32.bat
   * contrib/examples/pe/bld_vc.bat
   * contrib/examples/dbu/bld_b32.bat
   * contrib/examples/dbu/bld_vc.bat
   * contrib/examples/hscript/bld_b32.bat
   * contrib/examples/hscript/bld_vc.bat
   * utils/hbdoc/bld_vc.bat
   * utils/hbdoc/bld_b32.bat
   * utils/hbmake/bld_vc.bat
   * utils/hbmake/bld_b32.bat
 + Cleaning .c and .obj files after the build process.
 ! This is needed to not interfere with the GNU-make system, 
   which would pickup and try to compiler those temp .c files.
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek and all,

So, to give a short list of Windows .dll problems:

- 'sed' command line error.
- harbour*.dll naming in non-GNU make system.
- harbour.dll install location doesn't match in GNU ('lib') and non- 
GNU ('bin') builds.
- harbour.dll content doesn't match in GNU and non-GNU (missing  
hbcplr) builds.
- harbour.dll generated with BCC isn't compatible with MSVS and MinGW  
ones (due to added leading underscore in BCC).
- Minor: Generation of harbour.dll using the GNU-make system under  
Windows,
  needs full msys shell support. Maybe it would be better to include  
this

  process in the GNU-make system itself (if possible at all).
- MinGW generated shared-lib .exe is not compatible with MSVS generated
  harbour.dll. (missing '[EMAIL PROTECTED]' entry)

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Try it now. I've just committed workaround.
Seeing your other message I think that it can be caused by C:
drive specification. AFAIR MinGW support alternative /c/
*nix like path convention. Anyhow now it should work.


Okay. I did. There were only these sed command line problems:
--
./bin/postinst.sh
Generating C:/devl/hb_gcc/bin/hb-build...
Creating links...
c:\devl\MinGW-412\bin\sed.exe: -e expression #1, char 1: unknown  
command: `C'
c:\devl\MinGW-412\bin\sed.exe: -e expression #1, char 1: unknown  
command: `C'
c:\devl\MinGW-412\bin\sed.exe: -e expression #1, char 1: unknown  
command: `C'

Making harbour.dll...
make[1]: Entering directory `c:/work/harbour/harbour/source/vm'
gcc -I. -I../../include -mno-cygwin -Wall -W -march=pentiumpro -O4 - 
fomit-frame-pointer -ffast-math -c fm.c -ofm.o

make[1]: Leaving directory `c:/work/harbour/harbour/source/vm'
--

Difficult to tell how severe this is, but I now have harbour.dll
(although in 'lib', not in 'bin' as for the GNU-make files, NOTE:
we will need to fix that), and hb scripts properly installed. So it
looks good.

GNU sed in question is version 4.1.5 BTW.


I couldn't try the other was round, as I don't know
how to build hbtest.exe with harbour.dll dynamic lib
using MinGW. But I suspect it would work also.


Now the postinst.sh should be executed and it will create
hb* scripts.
So simply make:
  cd utils/hbtest
  for i in *.prg; do hbcmp -n -w -es2 $i; done
  hbcc -c rt_miscc.c
  hblnk *.o -gtstd -o hbtest -shared

Then replace harbour.dll created by MinGW with the one from MSVC
And relink the program:
  hblnk *.o -gtstd -o hbtest -shared
HBTEST should show different compiler note for MSVC...

or chose sth more simple:
  cd utils/hbrun
  hbmk -n -w -es2 hbrun -shared

then run it and execute:
  ? hb_compiler()


I've choosen the easiest, copied hbrun.prg to my bin install dir,
run 'hbmk -n -w -es2 hbrun -shared', and I got hbrun.exe. It runs
fine, after I copy harbour.dll from lib to bin.

If I try with MSVS .dll, I'm getting HB_FUN_HB_COMPILEBUFF
because GNU-make .dlls don't contain some libs, GNU-make made
.dlls do. [ BTW, isn't it a violation of our license to include
the compiler code in a .dll? ]

Anyway, after I remove those missing HB_COMPILE*() functions
from hbrun and recompile, I'm getting this: "The procedure
entry point [EMAIL PROTECTED] couldn't be located in the dynamic
link library harbour.dll".

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> I've manually built harbour.dll using the above method,

Try it now. I've just committed workaround.
Seeing your other message I think that it can be caused by C:
drive specification. AFAIR MinGW support alternative /c/
*nix like path convention. Anyhow now it should work.

> and I can now confirm that MSVS2005cpp, MSVS2005,
> MSVS2008cpp, MSVS2008 work with the MinGW built harbour.dll.
> I've tested with hbtest-dll.exe from each build.

Very nice.

> I couldn't try the other was round, as I don't know
> how to build hbtest.exe with harbour.dll dynamic lib
> using MinGW. But I suspect it would work also.

Now the postinst.sh should be executed and it will create
hb* scripts.
So simply make:
   cd utils/hbtest
   for i in *.prg; do hbcmp -n -w -es2 $i; done
   hbcc -c rt_miscc.c
   hblnk *.o -gtstd -o hbtest -shared

Then replace harbour.dll created by MinGW with the one from MSVC
And relink the program:
   hblnk *.o -gtstd -o hbtest -shared
HBTEST should show different compiler note for MSVC...

or chose sth more simple:
   cd utils/hbrun
   hbmk -n -w -es2 hbrun -shared

then run it and execute:
   ? hb_compiler()

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] 2008-08-05 15:23 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)

[Przemyslaw Czerpak]

2008-08-05 15:23 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)
  * harbour/bin/postinst.sh
* added workaround for wrongly detected harbour root path in some
  environments

  * harbour/source/vm/extrap.c
* minor modification

best regards
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek,

This is my starter batch file, if it helps:
--
@echo off

set PATH=C:\devl\MinGW-412\bin\;C:\devl\msys\1.0\bin\;%PATH%

set HB_INC_APOLLO=C:/devl/Apollo/include
set HB_INC_CURL=C:/devl/curl/include
set HB_INC_FIREBIRD=C:/devl/Firebird/include
set HB_INC_FREEIMAGE=C:/devl/FreeImage/Dist
set HB_INC_GD=C:/devl/gd/include
set HB_INC_LIBHARU=C:/devl/libharu/include
set HB_INC_MYSQL=C:/devl/mysql/include
set HB_INC_PGSQL=C:/devl/pgsql/include
set HB_INC_ADS=C:/devl/ADS900/ACESDK

set HB_INSTALL_PREFIX=C:/devl/hb_gcc
set HB_BIN_INSTALL=%HB_INSTALL_PREFIX%/bin
set HB_LIB_INSTALL=%HB_INSTALL_PREFIX%/lib
set HB_INC_INSTALL=%HB_INSTALL_PREFIX%/include
set HB_ARCHITECTURE=w32
set HB_COMPILER=mingw32
set PRG_USR=-l
set C_USR=-march=pentiumpro -O4 -fomit-frame-pointer -ffast-math
set L_USR=-s

sh make_gnu.sh %*
--

Brgds,
Viktor

On 2008.08.05., at 15:09, Przemyslaw Czerpak wrote:


On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,


./bin/postinst.sh
C:\work\harbour\harbour\bin\postinst.sh: ../bin/hb-func.sh: No such
file or directory
make: *** [install] Error 1


There is problem with dirname in you msys environment.
Looks that for ./bin/postinst.sh:
  dirname "$0"
returns "." instead of "./bin"
So far no one reported it. Please change in ./bin/postinst.sh[32]
   hb_root=".."
to:
   hb_root="."
It will help as temporary hack anyhow it will be good to find the
exact reason and fix the problem.
Probably you are using backslashes in your startup harbour directory
and it confuse dirname. I'll try to create some workaround for it.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

hb-mkslib.sh harbour.dll libhbvm.a libhbrtl.a libhbcommon.a  



but it's not necessary. ./make_gnu.sh install will be enough.


I've manually built harbour.dll using the above method,
and I can now confirm that MSVS2005cpp, MSVS2005,
MSVS2008cpp, MSVS2008 work with the MinGW built harbour.dll.
I've tested with hbtest-dll.exe from each build.

[ It didn't work with harbour-b32.dll of course, as this
one has a leading underscore on each exported symbol
(maybe a different calling convention too). I wonder
if using __stdcall [__export] with BCC32 couldn't solve
this problem. I tried to change HB_EXPORT to __export,
but so far it failed with different error messages. ]

I couldn't try the other was round, as I don't know
how to build hbtest.exe with harbour.dll dynamic lib
using MinGW. But I suspect it would work also.

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> ./bin/postinst.sh
> C:\work\harbour\harbour\bin\postinst.sh: ../bin/hb-func.sh: No such  
> file or directory
> make: *** [install] Error 1

There is problem with dirname in you msys environment.
Looks that for ./bin/postinst.sh:
   dirname "$0"
returns "." instead of "./bin"
So far no one reported it. Please change in ./bin/postinst.sh[32]
hb_root=".."
to:
hb_root="."
It will help as temporary hack anyhow it will be good to find the
exact reason and fix the problem.
Probably you are using backslashes in your startup harbour directory
and it confuse dirname. I'll try to create some workaround for it.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek,


Surely, it would be better. I believe all compilers should
be able to produce a compatible .dll.
Okay, I've now built Harbour using make_gnu.sh, I don't know
how a shared lib looks like, but there are surely not any
harbour*.dll created.


My fault, I forgot that harbour shared library is created in install
phase in HB_LIB_INSTALL directory. By default it's /usr/local/ 
harbour/lib

So please make now:
  ./make_gnu.sh install


Okay, now tried with 'install', and it does install everything,
but I don't see it installing any .dlls still. The end of the
process looks like this:

---
...
./bin/postinst.sh
C:\work\harbour\harbour\bin\postinst.sh: ../bin/hb-func.sh: No such  
file or directory

make: *** [install] Error 1
---


hb-mkslib.sh needs parameters, but I don't know what exactly?


If you want to create harbour.dll manually then make:

hb-mkslib.sh harbour.dll libhbvm.a libhbrtl.a libhbcommon.a  



but it's not necessary. ./make_gnu.sh install will be enough.


I'd like to get it automatically :)

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> Surely, it would be better. I believe all compilers should
> be able to produce a compatible .dll.
> Okay, I've now built Harbour using make_gnu.sh, I don't know
> how a shared lib looks like, but there are surely not any
> harbour*.dll created.

My fault, I forgot that harbour shared library is created in install
phase in HB_LIB_INSTALL directory. By default it's /usr/local/harbour/lib
So please make now:
   ./make_gnu.sh install

> hb-mkslib.sh needs parameters, but I don't know what exactly?

If you want to create harbour.dll manually then make:

hb-mkslib.sh harbour.dll libhbvm.a libhbrtl.a libhbcommon.a 

but it's not necessary. ./make_gnu.sh install will be enough.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Maybe this works in the MinGW shell environment,
but I tried it only once so far (in non-Harbour context),
so I'm highly unfamiliar with it.


Just click on MSys icon and then make:

  cd 
  ./make_gnu.sh


Okay it's now running. Pretty smoothly actually.

[ Only make_gnu.sh clean took quite a while to finish,
caused by some 'find' command on my whole harbour dir.
I wonder what is the purpose of this. ]


Overall, I think I'm leaving this topic for now, and we
will revisit it in a next revision. It's not a critical
issue after all.


Anyhow it will be good to check if MinGW is MSVC compatible.
If not then I do not see any reason to force MinGW and GNUC
users to use MSVC for creating official harbour.dll.
Please remember that GCC based binaries are most portable
between systems (in fact they can be created on all supported
by us systems) with support for cross builds and MSVC is compiler
which can be used only for very limited number of platforms.
If sth should be considered as official windows shared library
format then IMHO it should be compatible with MinGW harbour.dll.


Surely, it would be better. I believe all compilers should
be able to produce a compatible .dll.

Okay, I've now built Harbour using make_gnu.sh, I don't know
how a shared lib looks like, but there are surely not any
harbour*.dll created. hb-mkslib.sh needs parameters, but
I don't know what exactly?

How should I continue now?

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> Maybe this works in the MinGW shell environment,
> but I tried it only once so far (in non-Harbour context),
> so I'm highly unfamiliar with it.

Just click on MSys icon and then make:

   cd 
   ./make_gnu.sh

> Even if hb-mkslib worked
> in MinGW, how could I generate something like harbour.dll,
> when we don't have a libharbour.a to begin with?

>From existing *.a and *.o files.
>From mk-mkslib.sh:

   simple script to build shared libraries from static ones and
   object files

> Overall, I think I'm leaving this topic for now, and we
> will revisit it in a next revision. It's not a critical
> issue after all.

Anyhow it will be good to check if MinGW is MSVC compatible.
If not then I do not see any reason to force MinGW and GNUC
users to use MSVC for creating official harbour.dll.
Please remember that GCC based binaries are most portable
between systems (in fact they can be created on all supported
by us systems) with support for cross builds and MSVC is compiler
which can be used only for very limited number of platforms.
If sth should be considered as official windows shared library
format then IMHO it should be compatible with MinGW harbour.dll.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] 2008-08-05 13:22 UTC+0200 Viktor Szakats (harbour.01 syenar hu)

[Szakáts Viktor]

2008-08-05 13:22 UTC+0200 Viktor Szakats (harbour.01 syenar hu)
   * doc/whatsnew.txt
 + Added hbdot -> hbrun info.

   * utils/Makefile
 ! Missing change to previous commit.

   * contrib/examples/pp/bld_b32.bat
   * contrib/examples/guestbk/bld_b32.bat
   * contrib/examples/pe/bld_b32.bat
   * contrib/examples/dbu/bld_b32.bat
   * contrib/examples/hscript/bld_b32.bat
   * utils/hbdoc/bld_b32.bat
   * utils/hbmake/bld_b32.bat
 % -e switch removed from bcc32 command line.
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Przemyslaw Czerpak]

On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,

> Okay, my only problem is how to create harbour.dll
> with MinGW (or the GNU-make system in general)?

Just simply run make_gnu.sh from MSYS. It will create
harbour shared library automatically.

> [ BTW, maybe hbrtl.dll (or something else) would be
> a better name for harbour.dll, as it's current name
> implies that it's a dependency of harbour.exe. ]

For me it's very good name because it cleanly shows
what to look for when some applications shows that
harbour[.dll,.so,.dyn,...] is missing. hbrtl will
look to cryptic for final users.
BTW you can create harbour compiler binaries linked
with harbour.dll if you want to reduce the size.

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Lorenzo,


[ I suspect it's not supported. ]


I can't explain the details.

What I know is that if I want a dynamic lib I only need to pass the
object file to hb-mkslib and the result is a dynamic lib.

And if I want to get small exe I only need to change from -static to
-shared and the apps are "linked" against harbour.[so|dll|dylib]


I'd need this for Windows compilers, in this case MinGW.

Maybe this works in the MinGW shell environment,
but I tried it only once so far (in non-Harbour context),
so I'm highly unfamiliar with it. Even if hb-mkslib worked
in MinGW, how could I generate something like harbour.dll,
when we don't have a libharbour.a to begin with?

Overall, I think I'm leaving this topic for now, and we
will revisit it in a next revision. It's not a critical
issue after all.

Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Lorenzo Fiorini]

On Tue, Aug 5, 2008 at 12:53 PM, Szakáts Viktor <[EMAIL PROTECTED]> wrote:

> I have no plans to touch the GNU-make system
> in any ways this close to the release, I just
> simply have no idea how to do that currently,
> that's why I was asking.
>
> [ I suspect it's not supported. ]

I can't explain the details.

What I know is that if I want a dynamic lib I only need to pass the
object file to hb-mkslib and the result is a dynamic lib.

And if I want to get small exe I only need to change from -static to
-shared and the apps are "linked" against harbour.[so|dll|dylib]

best regards,
Lorenzo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Lorenzo,

I have no plans to touch the GNU-make system
in any ways this close to the release, I just
simply have no idea how to do that currently,
that's why I was asking.

[ I suspect it's not supported. ]

Brgds,
Viktor

On 2008.08.05., at 10:35, Lorenzo Fiorini wrote:

On Tue, Aug 5, 2008 at 9:38 AM, Szakáts Viktor [EMAIL PROTECTED]> wrote:



Okay, my only problem is how to create harbour.dll
with MinGW (or the GNU-make system in general)?


Simply to remind that GNU-make system is the same for
Linux/Windows/Mac OS X and many other OSes so every change should be
done carefully and tested in many different environments.

I don't know what is exactly your goal but I'd leave GNU make system
as it is since it's main goal is portability not host OS "tight"
integration.

best regards,
Lorenzo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

RE: [Harbour] Re: Clipper for web applications!

[Massimo Belgrano]

I am impressed by visual webgui demo at
http://samples.visualwebgui.com/MainForm.wgx
Is possible use as gui for harbour?

Do you know a demo for openlaszlo?
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Lautaro
Moreira
Sent: Monday, August 04, 2008 4:04 PM
To: harbour@harbour-project.org
Subject: [Harbour] Re: Clipper for web applications!

You forgot OpenLaszlo, it's pretty amazing on development of RIA web 2.0

apps it's opensource and free, and that uses SOAP, PlainHTML or XML as 
Exchaging Data Methods:


url : www.openlaszlo.org


Atte,

Lautaro Moreira

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] 2008-08-04 22:13 UTC+0200 Przemyslaw Czerpak (druzus/at/priv.onet.pl)

[Lorenzo Fiorini]

On Mon, Aug 4, 2008 at 10:15 PM, Przemyslaw Czerpak <[EMAIL PROTECTED]> wrote:

>  * harbour/source/rtl/hbinet.c
>! added protection against using wrong handles
>! fixed possible resource leak (unclosed handle) when open handle is
>  passed to HB_INETCONNECT[IP]()

Perfect!

Now if I run tt75s twice I don't get segfault and the error message is set to:

-4 Closed socket

best regards,
Lorenzo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

RE: [Harbour] harbour.dll revisited

[Massimo Belgrano]

Hbrtl01_00_00.dll for versioning

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Szakáts Viktor
Sent: Tuesday, August 05, 2008 9:39 AM
To: Harbour Project Main Developer List.
Subject: Re: [Harbour] harbour.dll revisited

Hi Przemek,

Okay, my only problem is how to create harbour.dll
with MinGW (or the GNU-make system in general)?

[ BTW, maybe hbrtl.dll (or something else) would be
a better name for harbour.dll, as it's current name
implies that it's a dependency of harbour.exe. ]

Brgds,
Viktor

On 2008.08.05., at 2:59, Przemyslaw Czerpak wrote:

> On Tue, 05 Aug 2008, Szakáts Viktor wrote:
>
> Hi Viktor,
>
>> Do we want to make any steps towards a standardized harbour.dll?
>> I'd suggest to rename harbour-vc.dll to harbour.dll as a step now.
>> This means we consider the MSVC compiler as the standard and
>> required tool to build our standard harbour.dll.
>
> Can you check if you can use MINGW harbour.dll with MSVC Harbour
> builds and the one created by MSVC with MINGW?
>
> best regards,
> Przemek
> ___
> Harbour mailing list
> Harbour@harbour-project.org
> http://lists.harbour-project.org/mailman/listinfo/harbour

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Lorenzo Fiorini]

On Tue, Aug 5, 2008 at 9:38 AM, Szakáts Viktor <[EMAIL PROTECTED]> wrote:

> Okay, my only problem is how to create harbour.dll
> with MinGW (or the GNU-make system in general)?

Simply to remind that GNU-make system is the same for
Linux/Windows/Mac OS X and many other OSes so every change should be
done carefully and tested in many different environments.

I don't know what is exactly your goal but I'd leave GNU make system
as it is since it's main goal is portability not host OS "tight"
integration.

best regards,
Lorenzo
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Re: [Harbour] harbour.dll revisited

[Szakáts Viktor]

Hi Przemek,

Okay, my only problem is how to create harbour.dll
with MinGW (or the GNU-make system in general)?

[ BTW, maybe hbrtl.dll (or something else) would be
a better name for harbour.dll, as it's current name
implies that it's a dependency of harbour.exe. ]

Brgds,
Viktor

On 2008.08.05., at 2:59, Przemyslaw Czerpak wrote:


On Tue, 05 Aug 2008, Szakáts Viktor wrote:

Hi Viktor,


Do we want to make any steps towards a standardized harbour.dll?
I'd suggest to rename harbour-vc.dll to harbour.dll as a step now.
This means we consider the MSVC compiler as the standard and
required tool to build our standard harbour.dll.


Can you check if you can use MINGW harbour.dll with MSVC Harbour
builds and the one created by MSVC with MINGW?

best regards,
Przemek
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour


___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] 2008-08-05 08:50 UTC+0200 Viktor Szakats (harbour.01 syenar hu)

[Szakáts Viktor]

2008-08-05 08:50 UTC+0200 Viktor Szakats (harbour.01 syenar hu)
   * harbour-ce-spec
   * harbour-w32-spec
   * harbour.spec
   * common.mak
   * make_b32.mak
   * make_gcc.mak
   * make_vc.mak
   * make_vcce.mak
   * make_tgz.sh
   * debian/rules
   - doc/man/hbdot.1
   * doc/man/hbrun.1
   - utils/hbdot
   * utils/hbrun/Makefile
   * utils/hbrun/hbrun.prg
   - utils/hbrun/external.prg
 * Replaced hbrun functionality with hbdot's.
 - Removed separate hbdot tool.

   * contrib/hbsqlit3/sqlite3/sqlite3.c
   * contrib/hbsqlit3/make_vc.bat
 ! Fixed bug in foreign code (sqlite3.c) to compile in 
   MSVC C++ mode. (HANDLE -> HMODULE)
 * C++ mode is no longer forced in non-GNU MSVC builds, 
   this way also avoiding a screen warning.

   * contrib/examples/dbu/bld_b32.bat
   * contrib/examples/dbu/bld_vc.bat
 ! Fixed to call 'patch' with '-N' so that it doesn't 
   ask to reverse patches when run multiple times.

   + utils/hbdoc/bld_b32.bat
   + utils/hbdoc/bld_vc.bat
 + Added non-GNU make batch files to build hbmake.
 ; This is a step towards detaching hbdoc from core.

   * utils/hbdoc/hbdocdef.ch
 ! Fixed equality operators to be SET EXACT independent.
 ; Minor formatting.
--
Brgds,
Viktor

___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour