As promised the complete xHarbour.com sources of ALL of our products, scripts, documentation, etc. have been uploaded to the xHarbour.org GitHub repository (including all commit history) into the xHarbourBuilder sub folder.

Enjoy!

Ron

Il 14/08/2023 20:26, Ron Pinkas ha scritto:

> As promised the complete xHarbour.com sources of ALL of our products, scripts, documentation, etc. have been uploaded to the xHarbour.org GitHub repository (including all commit history) into the xHarbourBuilder sub folder.

Thank you, Ron! Unfortunately, the new version of xHarbour from GitHub
is useless for me as it can't be built. I hope it will be fixed soon. In
the meantime I'll keep using the one from SVN.

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Hi Ron and Patrick,

Thanks for releasing the files/sources, i am working on a updated version of xhb.com with pellesc-12 32 and 64 bit also, they will be
available soon also.

regards,
Richard

Op maandag 14 augustus 2023 om 20:26:47 UTC+2 schreef Ron Pinkas:
> As promised the complete xHarbour.com sources of ALL of our products, scripts, documentation, etc. have been uploaded to the xHarbour.org GitHub repository (including all commit history) into the xHarbourBuilder sub folder.
>
> Enjoy!
>
> Ron

On Monday, August 14, 2023 at 2:15:06 PM UTC-5, Enrico Maria Giordano wrote:

> Thank you, Ron! Unfortunately, the new version of xHarbour from GitHub
> is useless for me as it can't be built. I hope it will be fixed soon. In
> the meantime I'll keep using the one from SVN.

Sorry Enrico, I somehow missed that - which O/S and Compiler? What error?

Ron

Em segunda-feira, 14 de agosto de 2023 às 15:26:47 UTC-3, Ron Pinkas escreveu:
> As promised the complete xHarbour.com sources of ALL of our products, scripts, documentation, etc. have been uploaded to the xHarbour.org GitHub repository (including all commit history) into the xHarbourBuilder sub folder.
>
> Enjoy!
>
> Ron

Ron,

Thank you.

The source code is under which license ?

I found this info:

https://github.com/ronpinkas/xharbour/blob/main/xHarbourBuilder/Free/ReadMe..rtf

"This distribution of xHarbour from http://free.xHarbour.com is made from a combination of free software as well as proprietary software from xHarbour..com Inc.

Special care should be given to making sure that you are absolutely clear on the License that apply to each respective component. Be advised that "xeditw.exe", "xbuild.exe", "xbuildw.exe", "XBScript.dll" and "xHarbour Language Reference Guide.chm" which is part of this distribution are NOT part of the xHarbour project, and are NOT subject to the GPL but are products from xHarbour.com Inc. which grants you the non exclusive right to use these files only in conjunction with xHarbour distributions from free.xHarbur.com. You are STRICTLY PROHIBITED from distributing any of these files to anyone else."

I would like to adapt SQLRDD to work with my fork of Harbour:

https://github.com/marcosgambeta/harbourpp-v1

But I dont want to violate any license. :-)

Il 14/08/2023 21:56, Ron Pinkas ha scritto:

>> Thank you, Ron! Unfortunately, the new version of xHarbour from GitHub
>> is useless for me as it can't be built. I hope it will be fixed soon. In
>> the meantime I'll keep using the one from SVN.
>
> Sorry Enrico, I somehow missed that - which O/S and Compiler? What error?

Warning W8004 source\pp\ppgen.c 717: 'szUTC' is assigned a value that is
never used in function hb_pp_parseChangelog

Warning W8056 obj\b32\comptool.c 631: Integer arithmetic overflow in
function hb_verCvsID

Warning W8056 obj\b32\hbrc.c 359: Integer arithmetic overflow in
function main
Warning W8056 obj\b32\hbrc.c 360: Integer arithmetic overflow in
function main
Warning W8056 obj\b32\hbrc.c 380: Integer arithmetic overflow in
function main
Warning W8056 obj\b32\hbrc.c 384: Integer arithmetic overflow in
function main

Error harbour.exe.rc 3 0: Too many digits in a number

And this is what I get using this batch for MSC32 (works fine with
xHarbour from SVN):

@ ECHO OFF

SET MSC=e:\msc32\msc
SET XHB=e:\msc32\xharbour

SET __MSC__=1
SET USE_MSVCRT=1

SET CC_DIR=%MSC%

SET CFLAGS=-O1

SET INCLUDE=%MSC%\include\ucrt;%MSC%\include;%MSC%\include\sdk
SET LIB=%MSC%\lib;%MSC%\lib\sdk

SET HB_DIR_OPENSSL=e:\xhbsvn\openssl-win32

SET HB_GUI=1
SET HB_NO_BACKGROUND=1
SET HB_NO_DV_MEMCPY=1
SET HB_NO_FM_DL_ALLOC=1
SET HB_NO_VM_ALL=1

CALL make_vc clean
CALL make_vc core
CALL make_vc contrib

PAUSE

Result:

Removing System and Object Files ...
Removing DLL and Object Files ...
Removing Contrib Libraries and Object Files ...
Done ...

****** End of Job *****
\NVIDIA non atteso.

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Enrico,

> Warning W8004 source\pp\ppgen.c 717: 'szUTC' is assigned a value that is
> never used in function hb_pp_parseChangelog
>
> Warning W8056 obj\b32\comptool.c 631: Integer arithmetic overflow in
> function hb_verCvsID
>
> Warning W8056 obj\b32\hbrc.c 359: Integer arithmetic overflow in
> function main
> Warning W8056 obj\b32\hbrc.c 360: Integer arithmetic overflow in
> function main
> Warning W8056 obj\b32\hbrc.c 380: Integer arithmetic overflow in
> function main
> Warning W8056 obj\b32\hbrc.c 384: Integer arithmetic overflow in
> function main
>
> Error harbour.exe.rc 3 0: Too many digits in a number

Please update and check after:

2023-08-14 18:04 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
* source/pp/ppgen.c
* Fixed compiler warnings caused by the auto generated /include/hbver.h

> And this is what I get using this batch for MSC32 (works fine with
> xHarbour from SVN):
> ...
> Result:
>
> Removing System and Object Files ...
> Removing DLL and Object Files ...
> Removing Contrib Libraries and Object Files ...
> Done ...
>
> ****** End of Job *****

I am not familiar with this, and sadly it does not provide any error info. I simply use make_vc.bat as it has builtin auto detection. Which specific version of Windows and MSC are you using? Can you try to see what is the actual error in the log files?

Ron

On Monday, August 14, 2023 at 3:57:51 PM UTC-5, marcosgambeta wrote:
> Em segunda-feira, 14 de agosto de 2023 às 15:26:47 UTC-3, Ron Pinkas escreveu:
> > As promised the complete xHarbour.com sources of ALL of our products, scripts, documentation, etc. have been uploaded to the xHarbour.org GitHub repository (including all commit history) into the xHarbourBuilder sub folder.
> >
> > Enjoy!
> >
> > Ron
> Ron,
>
> Thank you.
>
> The source code is under which license ?
>
> I found this info:
>
> https://github.com/ronpinkas/xharbour/blob/main/xHarbourBuilder/Free/ReadMe.rtf
>
> "This distribution of xHarbour from http://free.xHarbour.com is made from a combination of free software as well as proprietary software from xHarbour.com Inc.
>
> Special care should be given to making sure that you are absolutely clear on the License that apply to each respective component. Be advised that "xeditw.exe", "xbuild.exe", "xbuildw.exe", "XBScript.dll" and "xHarbour Language Reference Guide.chm" which is part of this distribution are NOT part of the xHarbour project, and are NOT subject to the GPL but are products from xHarbour.com Inc. which grants you the non exclusive right to use these files only in conjunction with xHarbour distributions from free.xHarbur.com. You are STRICTLY PROHIBITED from distributing any of these files to anyone else."
>
> I would like to adapt SQLRDD to work with my fork of Harbour:
>
> https://github.com/marcosgambeta/harbourpp-v1
>
> But I dont want to violate any license. :-)

For now I just uploaded the whole GIT as it was in our PRIVATE instance. The intent is to release all our software with the same License as the xHarbour RTL (GPL 2 or later at your choice), which means I will have to modify licenses included and/or add new licenses. Will do ASAP. Code that xHarbour.com did not own, such as the Pelle's C and any other 3rd party of course will remain the same. You are hereby specifically and explicitly given permission to use SQLRDD, Visual xHarbour, xEdit, xBuild, WinAPI, ActiveX, Apollo RDD, IEGui, Update Server, OleServer, RushMore, xBaseScript (ActiveScript), XDO subject to the terms of the GPL Version 2 or later, just as any other xHarbour RTL code.

Ron

Em segunda-feira, 14 de agosto de 2023 às 15:26:47 UTC-3, Ron Pinkas escreveu:
> As promised the complete xHarbour.com sources of ALL of our products, scripts, documentation, etc. have been uploaded to the xHarbour.org GitHub repository (including all commit history) into the xHarbourBuilder sub folder.
>
> Enjoy!
>
> Ron
Very good master.
I'm going to lower my head in these sources and try to compile with my project.

Leonardo Machado

Il 15/08/2023 01:24, Ron Pinkas ha scritto:

> Please update and check after:
>
> 2023-08-14 18:04 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
> * source/pp/ppgen.c
> * Fixed compiler warnings caused by the auto generated /include/hbver.h

Now I get:

source\compiler\hbmain.c:
Borland Resource Compiler Version 5.40
Copyright (c) 1990, 1999 Inprise Corporation. All rights reserved.

Error harbour.exe.rc 3 0: Too many digits in a number

And in the console I get:

Removing System and Object Files ...
Removing DLL and Object Files ...
Removing Contrib Libraries and Object Files ...
Done ...

****** End of Job *****
Creating System Files (ST) ...
Creating Contrib Libraries ...
Impossibile trovare l'etichetta batch specificata - CONTRIBS_ERR
Premere un tasto per continuare . . .

I'm compiling with BCC32 and the following batch:

@ ECHO OFF

CALL bcc32 /paths

SET CC_DIR=%BCC%

SET CFLAGS=-w!-

SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk

SET HB_DIR_OPENSSL=e:\xhbsvn\openssl-win32

SET HB_GUI=1
SET HB_NO_BACKGROUND=1
SET HB_NO_DV_MEMCPY=1
SET HB_NO_FM_DL_ALLOC=1
SET HB_NO_VM_ALL=1

CALL make_bc clean
CALL make_bc core
CALL make_bc contrib

PAUSE

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Il 15/08/2023 14:24, Enrico Maria Giordano ha scritto:

> CALL bcc32 /paths

Sorry, this is

SET BCC=e:\bcc32\bcc

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Em terça-feira, 15 de agosto de 2023 às 09:26:59 UTC-3, Enrico Maria Giordano escreveu:
> Il 15/08/2023 14:24, Enrico Maria Giordano ha scritto:
>
> > CALL bcc32 /paths
>
> Sorry, this is
>
> SET BCC=e:\bcc32\bcc
> --
> Enrico Maria Giordano
>
> http://www.emagsoftware.it
> http://www.emagsoftware.it/emgmusic
> http://www.emagsoftware.it/spectrum
> http://www.emagsoftware.it/tbosg
If someone manages to compile with vc22+, please post the steps here

Il 15/08/2023 01:24, Ron Pinkas ha scritto:

>> And this is what I get using this batch for MSC32 (works fine with
>> xHarbour from SVN):
>> ...
>> Result:
>>
>> Removing System and Object Files ...
>> Removing DLL and Object Files ...
>> Removing Contrib Libraries and Object Files ...
>> Done ...
>>
>> ****** End of Job *****
>
> I am not familiar with this, and sadly it does not provide any error info. I simply use make_vc.bat as it has builtin auto detection. Which specific version of Windows and MSC are you using? Can you try to see what is the actual error in the log files?

Sorry, no logs are generated. The execution of the batch is immediately
stopped and all what I get is this in the console:

Removing System and Object Files ...
Removing DLL and Object Files ...
Removing Contrib Libraries and Object Files ...
Done ...

****** End of Job *****
\NVIDIA non atteso.

I'm using this batch (please note that it is working fine with SVN
versionof xHarbour):

@ ECHO OFF

SET MSC=e:\msc32\msc

SET __MSC__=1
SET USE_MSVCRT=1

SET CC_DIR=%MSC%

SET CFLAGS=-O1

SET INCLUDE=%MSC%\include\ucrt;%MSC%\include;%MSC%\include\sdk
SET LIB=%MSC%\lib;%MSC%\lib\sdk

SET HB_DIR_OPENSSL=e:\xhbsvn\openssl-win32

SET HB_GUI=1
SET HB_NO_BACKGROUND=1
SET HB_NO_DV_MEMCPY=1
SET HB_NO_FM_DL_ALLOC=1
SET HB_NO_VM_ALL=1

CALL make_vc clean
CALL make_vc core
CALL make_vc contrib

PAUSE

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Il 15/08/2023 14:31, Marco Aurélio ha scritto:

> If someone manages to compile with vc22+, please post the steps here

I'm using this compiler and it is working fine with SVN version of
xHarbour, so the problem lies in one of the recent changes.

Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86

(Date: 20220531)

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Em terça-feira, 15 de agosto de 2023 às 09:38:37 UTC-3, Enrico Maria Giordano escreveu:
> Il 15/08/2023 14:31, Marco Aurélio ha scritto:
>
> > If someone manages to compile with vc22+, please post the steps here
> I'm using this compiler and it is working fine with SVN version of
> xHarbour, so the problem lies in one of the recent changes.
>
> Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
>
> (Date: 20220531)
> --
> Enrico Maria Giordano
>
> http://www.emagsoftware.it
> http://www.emagsoftware.it/emgmusic
> http://www.emagsoftware.it/spectrum
> http://www.emagsoftware.it/tbosg
Can you compile SQLRDD with VC22+?

Il 15/08/2023 15:09, Marco Aurélio ha scritto:

> Can you compile SQLRDD with VC22+?

How to do it, exactly?

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

On Tuesday, August 15, 2023 at 7:32:01 AM UTC-5, Marco Aurélio wrote:
> Em terça-feira, 15 de agosto de 2023 às 09:26:59 UTC-3, Enrico Maria Giordano escreveu:
> > Il 15/08/2023 14:24, Enrico Maria Giordano ha scritto:
> >
> > > CALL bcc32 /paths
> >
> > Sorry, this is
> >
> > SET BCC=e:\bcc32\bcc
> > --
> > Enrico Maria Giordano
> >
> > http://www.emagsoftware.it
> > http://www.emagsoftware.it/emgmusic
> > http://www.emagsoftware.it/spectrum
> > http://www.emagsoftware.it/tbosg
> If someone manages to compile with vc22+, please post the steps here

If you install (free) VS 2022 using default installer settings (not changing tareget folders) than you should build no problem by just:

cd \xharbour
make_vc clean
make_vc

Works for me perfectly.

Em terça-feira, 15 de agosto de 2023 às 11:18:30 UTC-3, Ron Pinkas escreveu:
> On Tuesday, August 15, 2023 at 7:32:01 AM UTC-5, Marco Aurélio wrote:
> > Em terça-feira, 15 de agosto de 2023 às 09:26:59 UTC-3, Enrico Maria Giordano escreveu:
> > > Il 15/08/2023 14:24, Enrico Maria Giordano ha scritto:
> > >
> > > > CALL bcc32 /paths
> > >
> > > Sorry, this is
> > >
> > > SET BCC=e:\bcc32\bcc
> > > --
> > > Enrico Maria Giordano
> > >
> > > http://www.emagsoftware.it
> > > http://www.emagsoftware.it/emgmusic
> > > http://www.emagsoftware.it/spectrum
> > > http://www.emagsoftware.it/tbosg
> > If someone manages to compile with vc22+, please post the steps here
> If you install (free) VS 2022 using default installer settings (not changing tareget folders) than you should build no problem by just:
>
> cd \xharbour
> make_vc clean
> make_vc
>
> Works for me perfectly.
Hi Ron, this will compile libs in xHarbourBuilder folder?

On Tuesday, August 15, 2023 at 8:24:56 PM UTC+8, Enrico Maria Giordano wrote:
> Il 15/08/2023 01:24, Ron Pinkas ha scritto:
>
> > Please update and check after:
> >
> > 2023-08-14 18:04 UTC-0500 Ron Pinkas <ronpinkas/AT/gmail/com>
> > * source/pp/ppgen.c
> > * Fixed compiler warnings caused by the auto generated /include/hbver.h
> Now I get:
>
> source\compiler\hbmain.c:
> Borland Resource Compiler Version 5.40
> Copyright (c) 1990, 1999 Inprise Corporation. All rights reserved.
> Error harbour.exe.rc 3 0: Too many digits in a number
> And in the console I get:
> Removing System and Object Files ...
> Removing DLL and Object Files ...
> Removing Contrib Libraries and Object Files ...
> Done ...
>
> ****** End of Job *****
> Creating System Files (ST) ...
> Creating Contrib Libraries ...
> Impossibile trovare l'etichetta batch specificata - CONTRIBS_ERR
> Premere un tasto per continuare . . .
>
>
> I'm compiling with BCC32 and the following batch:
>
> @ ECHO OFF
>
> CALL bcc32 /paths
>
> SET CC_DIR=%BCC%
>
> SET CFLAGS=-w!-
>
> SET LFLAGS=-L%BCC%\lib;%BCC%\lib\psdk
> SET HB_DIR_OPENSSL=e:\xhbsvn\openssl-win32
>
> SET HB_GUI=1
> SET HB_NO_BACKGROUND=1
> SET HB_NO_DV_MEMCPY=1
> SET HB_NO_FM_DL_ALLOC=1
> SET HB_NO_VM_ALL=1
> CALL make_bc clean
> CALL make_bc core
> CALL make_bc contrib
>
> PAUSE
> --
> Enrico Maria Giordano
>
> http://www.emagsoftware.it
> http://www.emagsoftware.it/emgmusic
> http://www.emagsoftware.it/spectrum
> http://www.emagsoftware.it/tbosg

the Borland Resource Compiler only support 2 or 3 digit version code only ,maybe u try to compile with Embarcadero C++ 10.2 ‘Tokyo’ Compiler

Enrico,

> I'm using this compiler and it is working fine with SVN version of
> xHarbour, so the problem lies in one of the recent changes.
>
> Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31329 for x86
> http://www.emagsoftware.it/tbosg

You are using a NON STANDARD Install of VS2022 (Your batch file shows MSC=e:\msc32\msc ). I believe the problem is with latest make_vc.bat not supporting such a configuration. I would strongly recommend a STANDARD INSTALL of VS 2022 and using plain make_vc.bat - works for me perfectly.

Ron

> > cd \xharbour
> > make_vc clean
> > make_vc
> >
> Hi Ron, this will compile libs in xHarbourBuilder folder?

No. We provided all our sources and build procedures, which obviously were using OUR tools. But since xBuild project files are provided you should be able to easily change xCC to MSVC. Naturally there may be some challenges, but please don't expect us to also support what we just donated free of charge.

Ron

Em terça-feira, 15 de agosto de 2023 às 11:29:15 UTC-3, Ron Pinkas escreveu:
> > > cd \xharbour
> > > make_vc clean
> > > make_vc
> > >
> > Hi Ron, this will compile libs in xHarbourBuilder folder?
> No. We provided all our sources and build procedures, which obviously were using OUR tools. But since xBuild project files are provided you should be able to easily change xCC to MSVC. Naturally there may be some challenges, but please don't expect us to also support what we just donated free of charge.
>
> Ron
Hi, Ron, Thanks again for all your efforts and support

Il 15/08/2023 16:18, Ron Pinkas ha scritto:

> If you install (free) VS 2022 using default installer settings (not changing tareget folders) than you should build no problem by just:
>
> cd \xharbour
> make_vc clean
> make_vc
>
> Works for me perfectly.

Sorry, but you should revert the modification that broke the build
process. Otherwise I can't use the GitHub version of xHarbour.

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Il 15/08/2023 16:23, Ron Pinkas ha scritto:

> You are using a NON STANDARD Install of VS2022 (Your batch file shows MSC=e:\msc32\msc ). I believe the problem is with latest make_vc.bat not supporting such a configuration. I would strongly recommend a STANDARD INSTALL of VS 2022 and using plain make_vc.bat - works for me perfectly.

Please revert make_vc.bat to the SVN version, it is working fine! We
must be free to change the compiler directory!

--
Enrico Maria Giordano

http://www.emagsoftware.it
http://www.emagsoftware.it/emgmusic
http://www.emagsoftware.it/spectrum
http://www.emagsoftware.it/tbosg

Enrico,

> > You are using a NON STANDARD Install of VS2022 (Your batch file shows MSC=e:\msc32\msc ). I believe the problem is with latest make_vc.bat not supporting such a configuration. I would strongly recommend a STANDARD INSTALL of VS 2022 and using plain make_vc.bat - works for me perfectly.

> Please revert make_vc.bat to the SVN version, it is working fine! We
> must be free to change the compiler directory!

make_vc has been cleaned, standardized to provide more consistent support to the many complexities and different tools installed by Microsoft. Support was also added for newer versions of all tools and the O/S itself. So your request to revert seems the wrong approach, instead we should find the exact cause of your issue, by tracing/debugging the build process. You should be able to easily find the actual problem and I will gladly assist in fixing. Luckily a batch file is not that difficult to debug. :)

Ron