Binary, Source, and Contrib files built under Harbour 3.4.0dev for MinGW 7.2 available for download

[Mel Smith]

Hi All (and especially Massimo) :

As a result of urging from Massimo Belgrano, I have now made available the following files available for download from whosaway.com

   hb3432_bin_mingw_1711151334.zip -- binary only (but with test .prg files included)

   hb3432_src_mingw_1711151334.zip -- source code only

   hb3432_con_mingw_1711151334.zip -- contrib code only

This compilation was done with methods suggested from Viktor thru Massimo  re: the msys32 sub-dir and CLANG/LLVM files.

I have tested harbour.exe (in the binary file), and used it to build successfully the speedtst.prg copied from my Harbour 3.2 installation. This speedtst runs at 14.21 seconds on my Asus lpatop. 

 

Unfortunately, I cannot build BCC 7.3.0 under Harbour 3.4 yet.  I'm still waiting for help from 'anyone' ??

-Mel

[Andi Jahja]

Hi Mel,

 

I am very sorry again for not having time yet to clean up the makefiles :(

 

Anyhow, if you would distribute the binary, please download at the:

 

http://www.mediafire.com/file/gew5pdf11ye6ayb/harbour_3.4_win64_bcc73_201711152334.7z
http://www.mediafire.com/file/vxjnjdlxk1mipzn/harbour_3.4_win32_bcc73_201711152334.7z

https://sourceforge.net/projects/xhrb/files/Private%20Builds/harbour_3.4_win64_bcc73_201711152334.7z/download
https://sourceforge.net/projects/xhrb/files/Private%20Builds/harbour_3.4_win32_bcc73_201711152334.7z/download

 

As usual, they are merely BIN + LIB + INCLUDE.

 

Andi

[Massimo Belgrano]

Thanks Very thanks!
I have download for   3.4 !

is Harbour 3.2.0dev r(1711152234) made with msys32 

now I hope that also harbour nighty follow this way

if you post your batch for compile & publish other may learn

with bcc 7.3 you have a problem only with harbour 3.4?
Here i invite anybody who  found a way of compiler hb34 and bcc73  describe it with batch

--
You received this message because you are subscribed to the Google Groups "Harbour Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Massimo Belgrano
Delta Informatica S.r.l. (Cliccami per scoprire ) 

[José Quintas]

https://www.embarcadero.com/free-tools/ccompiler

Installing and Using the Embarcadero C++ 10.1 Berlin Command-line Compiler.txt
(Embarcadero Freeware Software License Agreement)

Embarcadero C++ 7.20 for Win32 Copyright (c) 2012-2016 Embarcadero Technologies, Inc.
bcc32.exe: error: no input files

bcc32.exe -I. -I../../../../../../include -c -q -tWM -CP437 -w-sig- -w-aus- -w-ccc- -w-csu- -w-par- -w-rch- -w-ucp- -w-use- -w-prc- -w-pia- -d -O2 -OS -Ov -Oc -Oi -6 -DUNICODE "-Id:/github/harbour34/src/3rd/zlib" -DPNG_NO_STDIO +nul -I"d:\harbour\comp\bcc101\bin\..\Include" -I"d:\harbour\comp\bcc101\bin\..\Include\windows\crtl" -I"d:\harbour\comp\bcc101\bin\..\Include\windows\sdk" -opngget.obj ../../../pngget.c
Warning: option '-w-sig-' is not supported in Clang-based compiler.
Warning: option '-w-aus-' is not supported in Clang-based compiler.
Warning: option '-w-ccc-' is not supported in Clang-based compiler.
Warning: option '-w-csu-' is not supported in Clang-based compiler.
Warning: option '-w-par-' is not supported in Clang-based compiler.
Warning: option '-w-rch-' is not supported in Clang-based compiler.
Warning: option '-w-ucp-' is not supported in Clang-based compiler.
Warning: option '-w-use-' is not supported in Clang-based compiler.
Warning: option '-w-prc-' is not supported in Clang-based compiler.
Warning: option '-w-pia-' is not supported in Clang-based compiler.
Warning: option '-OS' is not supported in Clang-based compiler.
Warning: option '-Ov' is not supported in Clang-based compiler.
Warning: option '-Oc' is not supported in Clang-based compiler.
Warning: option '-Oi' is not supported in Clang-based compiler.
Warning: option '-6' is not supported in Clang-based compiler.

1) Shows 10.1, but 7.2 when run
2) Shows "clang based compiler", not sure if this means ready for Harbour 3.4 clang
3) Free as single user license

Not sure about 7.3 version

José M. C. Quintas

--
You received this message because you are subscribed to the Google Groups "Harbour Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to harbour-deve...@googlegroups.com.

[vszakats]

3.4 is automatically rebuilt for Windows after each commit,

so if somebody is interested in these builds, which are made

reproducibly (meaning builds for the same source revision

result in bit-identical binary outputs), in secure environments,

with publicly verifiable logs and downloads offered from proven,

open servers via secure protocols, you can head to:

   https://github.com/vszakats/harbour-core/releases

(binaries are in fact (cross-)built for Windows in three

environments: Linux, macOS and Windows — they are

functionally equivalent)

Matching source code can be downloaded and automatically

merged into the binary tree via a provided getsrc.sh script

(it's quite trivial, so can be converted to manual steps/batch

easily.). With the source code downloaded, it's easy to rebuild,

or build any contrib with customized dependencies provided

locally.

These binary packages also contain every necessary

components to use current latest libcurl + openssl 1.1 (with

http/2 support and libssh2 for sftp/scp). These 3rd party

binaries are also built in public, verifiable ways. See: [1]

These builds are always (and automatically so) built using the

current latest mingw-w64 toolchain with the current latest

llvm/clang compiler and contain all necessary libraries to create

apps for both 32-bit and 64-bit apps. llvm/clang-built binaries

(libs and dlls) are compatible with mingw-gcc built ones.

Included Harbour toolchain binaries (e.g. hbmk2.exe) are

built in 64-bit mode, so you'll need a development machine

running 64-bit Windows. These run more efficiently (= faster)

on modern hardware/OS, while still capable of creating 32-bit

apps.

[1] https://github.com/vszakats/harbour-deps

-Viktor

[Mel Smith]

Hi Massimo:

On Thursday, November 16, 2017 at 2:35:00 AM UTC-7, Massimo Belgrano wrote:

Thanks Very thanks!
I have download for   3.4 !

is Harbour 3.2.0dev r(1711152234) made with msys32

   No, only 3.4 is made with msys for now ... 

 

now I hope that also harbour nighty follow this way

if you post your batch for compile & publish other may learn

 

   Mymany batch files are very intertwined and much too complex to understand  -- even for *me* !

 

with bcc 7.3 you have a problem only with harbour 3.4?
Here i invite anybody who  found a way of compiler hb34 and bcc73  describe it with batch

   I hope Viktor will consider looking at the problem.  Andi has apparently solved it, but he, too, has difficulty unwinding all his batch and make files for my usage,

 

-Mel

[vszakats]

It's the known BCC 5.x PP bug. Interestingly they still haven't

fixed it in newer versions. There is a self-contained/minimal

example in ChangeLog.txt, you can report it to the company.

As said earlier, BCC (all versions) is deprecated in the 3.4

branch, it means no plans for more BCC workarounds, tweaks.

Existing BCC support is promised to be kept till 2017-12-31.

-Viktor

[Massimo Belgrano]

A good info is that  Have been compiled Harbour 3.4.0dev, MSYS64, CLang e Qt5xHb!

https://groups.google.com/forum/#!topic/qtxhb-br/ww2pkwyShCY

Here for show advantages CLang vs GCC

https://clang.llvm.org/comparison.html
https://clang.llvm.org/features.html#performance
https://clang.llvm.org/compatibility.html#cxx

--
You received this message because you are subscribed to the Google Groups "Harbour Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mel Smith]

Hi All:

   I have just built and tested a 64-bit Harbour 3.4 executable built under msys64 with mingw64 and clang64.  Again, I used the source code speedtst.prg from Harbour 3.2 for testing. All sections compiled without failure, and my speed was 11.95 seconds on my older Asus laptop.

   The links are posted on whosaway.com for your perusal and download if you wish..

-Mel

 

[Massimo Belgrano]

Thanks 
afaik you not include mingw and clang downloaded with msys   
 

--

You received this message because you are subscribed to the Google Groups "Harbour Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Massimo Belgrano]

Publishing your batch files is a way for documenting and found a good and clear solution
other user can start from your batch and evolve it

[Mel Smith]

On Monday, November 20, 2017 at 7:56:02 AM UTC-7, Massimo Belgrano wrote:

Publishing your batch files is a way for documenting and found a good and clear solution
other user can start from your batch and evolve it

Hi Massimo:

   Following is a list of just a *few* of my recent batch files involved in creating my downloads for whosaway.com  But, I also have three harbour 3.2 *executables* (created under BCC 7.3) that I use for building and updating my site from *many* template fragments. And aside from these batch files, I have many text files (.txt) that I use for input to the batch files.

   My service has always been to provide Harbour (and xHarbour) language builds for those users who don't want to build Harbour themselves. I believe several of my 343 download users also provide download services themselves  of these files.

   You, yourself, provided me with a fairly simple, and comprehensive method of producing 3.4 builds.  So, *you* are probably the best person for expanding the knowledge of the rest of the group. Currently, I am trying to understand the relationship between GCC and CLANG. The more I read, the more confused I am:  If we have Clang under msys32 and msys64, then why do we need MinGW32, and MinGW64 in that same sub-dir ?  So, if I don't understand this relationship, then I understand *nothing* :((

Anyway, here are just a few of the batch files that are used in creation of the builds:

-Mel Smith.

10/02/2017  02:38 PM             2,930 MAKEHARB.BAT

10/03/2017  08:50 AM             2,198 ming720.bat

10/03/2017  09:17 AM               817 BLDGYZIP.BAT

10/03/2017  09:23 AM             8,965 MAKENEW.BAT

10/03/2017  11:57 AM               117 HBUPD64.BAT

10/03/2017  12:33 PM               609 bldhrbmg64.bat

10/11/2017  09:28 AM               847 bldbcc3432zip.bat

11/09/2017  09:38 PM               371 hbupd34.bat

11/09/2017  10:23 PM               105 hbupd3464.bat

11/09/2017  10:33 PM               105 hbupd3432.bat

11/10/2017  08:32 AM               318 test3464.bat

11/10/2017  08:32 AM               280 test3432.bat

11/13/2017  09:42 AM             1,676 bld3432.bat

11/13/2017  11:21 AM               935 copymgw3432.bat

11/13/2017  04:59 PM             2,671 makehb34.bat

11/13/2017  05:13 PM             1,260 BLDMGW3432ZIP.BAT

11/14/2017  07:40 PM               946 bldhrbmg.bat

11/17/2017  04:41 PM             1,676 bld3464.bat

11/17/2017  04:50 PM             1,260 bldmgw3464zip.bat

11/17/2017  04:52 PM               935 copymgw3464.bat

11/18/2017  08:09 AM             2,761 makehb3464.bat

11/18/2017  08:23 AM             2,069 bldspeed.bat

             120 File(s)        131,715 bytes

               0 Dir(s)  220,495,847,424 bytes free

 

... and some text input files :

02/02/2017  09:14 AM               398 BZIPLIST.TXT

02/04/2017  05:20 PM               327 7264list.txt

02/04/2017  05:20 PM               327 7364list.txt

10/11/2017  08:51 AM               338 bzip3432list.txt

11/12/2017  12:38 PM               471 hb3432mgwbld.txt

11/13/2017  05:37 PM               150 hb3432mgwziplist.txt

11/15/2017  09:55 PM                10 VCbuild.txt

11/15/2017  09:56 PM                10 MGbuild.txt

11/15/2017  09:56 PM                10 BCbuild.txt

11/17/2017  04:51 PM               150 hb3464mgwziplist.txt

11/20/2017  08:19 AM                 4 hbdlddir.txt

11/20/2017  08:19 AM                10 CLbuild.txt

              76 File(s)      8,290,696 bytes

               0 Dir(s)  220,138,483,712 bytes free

[vszakats]

On Monday, November 20, 2017 at 3:56:02 PM UTC+1, Massimo Belgrano wrote:

Publishing your batch files is a way for documenting and found a good and clear solution
other user can start from your batch and evolve it

Maybe someone else is interested in this: The default 3.4

snapshot builds not only use public environments and logs,

but they do use _public scripts_ only, all of them hosted

inside the Habour repository itself.

-Viktor

[Massimo Belgrano]

Where is compilation  "batch" for windows and where is executed ?

Where is distrubition batch for windows  and where is executed ?
same for linux/max Os?

--
You received this message because you are subscribed to the Google Groups "Harbour Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-devel+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[vszakats]

On Monday, November 20, 2017 at 5:45:08 PM UTC+1, Massimo Belgrano wrote:

Where is compilation  "batch" for windows and where is executed ?

Where is distrubition batch for windows  and where is executed ?
same for linux/max Os?

Scripts are in the 'package' directory. They are all (portable) POSIX

shell scripts, not batches, so they'll need MSYS2 on Windows.

It's started here on Windows:

https://github.com/vszakats/harbour-core/blob/baf3a4d07fcf901db55e05f562e44d2cfa475624/.appveyor.yml#L63

Cross-build and Linux/macOS builds are launched via:

https://github.com/vszakats/harbour-core/blob/master/.travis.yml

The scripts will also work when launched standalone on a normal

desktop, though in this case the environment may need to be

prepared to meet some requirements, like required base tools,

like MSYS2, Homebrew (on macOS) or Docker (on Linux, though

not necessarily required) installed, etc.

-Viktor