2025-10-21 13:20 UTC+0200 Aleksander Czajczynski (hb fki.pl)

[Aleksander Czajczynski]

2025-10-21 13:20 UTC+0200 Aleksander Czajczynski (hb fki.pl)
* contrib/hbssl/hbssl.hbc
! actually target VS 2017 for libcrypto, libssl

* utils/hbmk2/hbmk2.prg
! slight rework of MSVC version detection, so it actually operates
with empty cPath_CompC variable

* also try to discover version number of future MSVC releases

* with Zig building GUI applications on Windows, hbmk2 will
now pass -Wl,/subsystem:windows to the linker


Best regards, Aleksander

[Mario H. Sabado]

Many thanks for this update Aleksander!

libssl and libcrypto are already automatically linked under MSVC without manually setting HB_COMPILER_VER value.

-gui switch already works with hbmk2 when using Zig.

Just amazed with the speed of Zig's win-make clean/win-make -j8.  It's 3-4x faster with other compilers when I parallel test it just for curiosity.

Best regards,

Mario

--
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.
To view this discussion visit https://groups.google.com/d/msgid/harbour-devel/68F76F33.5000105%40fki.pl.

[Aleksander Czajczynski]

Mario H. Sabado wrote:
> Many thanks for this update Aleksander!
>
> libssl and libcrypto are already automatically linked under MSVC
> without manually setting HB_COMPILER_VER value.
>
> -gui switch already works with hbmk2 when using Zig.
>
> Just amazed with the speed of Zig's win-make clean/win-make -j8. It's
> 3-4x faster with other compilers when I parallel test it just for
> curiosity.
>

That's interesting result, thanks for testing..

I can't tell if it's any better to use Zig as compiler instead of clang,
especially if you target only one platform. But the achievement here is
today's version of what probably WATCOM tried before, single tool -
compiler that carries multiple C headers and runtimes- reaching many
different platforms. Apart of that Zig is also a language on it's own -
positioned as C replacement with manual memory management.

Best regards, Aleksander

[Mario H. Sabado]

Zig uses the same LLVM standard with Clang for C/C++ code compilation so I think there's no big difference if ever in my opinion.

Yes, that's one great feature of Zig I think as compared with other existing compilers, that you can target different platforms and/or architecture (64/32 bit).

Best regards,

Mario

 

Best regards, Aleksander


--
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.

To view this discussion visit https://groups.google.com/d/msgid/harbour-devel/68F8AEA6.5060303%40fki.pl.

[Mario H. Sabado]

HI Aleksander,

May I request to separate the zig in the hbssl.hbc?  Under Zig, it's searching for ssl/crypto contrary to MSVC/MingW/Clang's libssl/libcrypto

{!HB_DYNBIND_OPENSSL&win&zig}libs=ssl crypto

Thanks and regards,

Mario

--
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.

To view this discussion visit https://groups.google.com/d/msgid/harbour-devel/68F8AEA6.5060303%40fki.pl.

[Aleksander Czajczynski]

Hi Mario!

Mario H. Sabado wrote:

May I request to separate the zig in the hbssl.hbc?  Under Zig, it's searching for ssl/crypto contrary to MSVC/MingW/Clang's libssl/libcrypto

{!HB_DYNBIND_OPENSSL&win&zig}libs=ssl crypto

Isn't it the same?

{!HB_DYNBIND_OPENSSL&win&(allmingw|clang|zig)}libs=ssl crypto

https://github.com/harbour/core/blob/master/contrib/hbssl/hbssl.hbc#L18

Of course it's confusing. Clang based tools depending on lld-linker backend is able to either go for lib{name}.a or {name}.lib
OpenSSL is not following this standard on Windows platform, because they left lib{name}.lib for linking.

I will excersise Zig  more in oncoming few days, hopefully on Windows too.

Best regards, Aleksander

To view this discussion visit https://groups.google.com/d/msgid/harbour-devel/CAGuBOFoS2pgUujoKrLFMh7da3dMbboUPX0Dsy7seaKJ%3DXdoxXw%40mail.gmail.com.

[Mario H. Sabado]

Hi Aleksander,

On Mon, Oct 27, 2025 at 6:46 PM Aleksander Czajczynski <h...@fki.pl> wrote:

Hi Mario!

Mario H. Sabado wrote:

May I request to separate the zig in the hbssl.hbc?  Under Zig, it's searching for ssl/crypto contrary to MSVC/MingW/Clang's libssl/libcrypto

{!HB_DYNBIND_OPENSSL&win&zig}libs=ssl crypto

Isn't it the same?

{!HB_DYNBIND_OPENSSL&win&(allmingw|clang|zig)}libs=ssl crypto

https://github.com/harbour/core/blob/master/contrib/hbssl/hbssl.hbc#L18

Of course it's confusing. Clang based tools depending on lld-linker backend is able to either go for lib{name}.a or {name}.lib
OpenSSL is not following this standard on Windows platform, because they left lib{name}.lib for linking.

I will excersise Zig  more in oncoming few days, hopefully on Windows too.

Indeed a bit confusing because allmingw and clang is searching for libssl/libcrypto whilst zig search or ssl/crypto.  Kindly ignore this for now.  I just copied the libssl.lib / libcrypto.lib to ssl.lib /crypto.lib.  It tries to search for ssl.lib or libssl.a.

Best regards,

Mario

 

To view this discussion visit https://groups.google.com/d/msgid/harbour-devel/68FF4D79.5090703%40fki.pl.