[Solved] New AddonManager requires OpenSSL 1.1.1 or above

[Syres]

I've been testing the new Win LP build 0.20.26845 (LibPack 12.5.4) which includes the new AddonManager. While it works OK on the whole, there is a series of warnings about failing to connect to URLs followed by:

Code: Select all

11:59:05  QSslSocket: OpenSSL >= 1.1.1 is required; OpenSSL 1.1.0j  20 Nov 2018 was found instead

Could the Libpack be upgraded to include OpenSSL 1.1.1 or is there a later LibPack with this version already in existence?


OS: Windows 7 Version 6.1 (Build 7601: SP 1)
Word size of FreeCAD: 64-bit
Version: 0.20.26845 (Git)
Build type: Release
Branch: master
Hash: 4430e3ec8c8050560478564a493e925bd7c5985a
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.0
Locale: English/United Kingdom (en_GB)

[chennes]

The specs you state here are not LibPack 12.5.4 (which includes OpenSSL 1.1.1l, and also OCCT 7.5.3). Can you double-check your output from cMake?

[Syres]

The specs you state here are not LibPack 12.5.4 (which includes OpenSSL 1.1.1l, and also OCCT 7.5.3). Can you double-check your output from cMake?

I'm purely going off the name of the compiled .7z file which includes Win-LPv12.5.4 at the top of the list of assets here https://github.com/FreeCAD/FreeCAD-Bund ... kly-builds so I am making an assumption but a reasonable one!!

@sgrogan kindly compiled it on my request.

Could you give some input please, I feel 'piggy in the middle'

[chennes]

Let's ping @srogan then, because those library versions don't all match up to LibPack 12.5.4, so something is going wrong with the compile there.

Ping

[kisolre]

this is the result frome my local build which uses a recent 12.5.4. libpack downloaded from here https://github.com/apeltauer/FreeCAD/re ... ack_12.5.4
It strangely reports OCC as 7.5.0 and not 7.5 3. Not sure how to check actual OpenSSL version.

OS: Windows 8.1 Version 6.3 (Build 9600)
Word size of FreeCAD: 64-bit
Version: 0.20.26847 (Git)
Build type: Release
Branch: master
Hash: 138418ef30859d70aeed8b95e0cc81765683cfd4
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.0
Locale: Bulgarian/Bulgaria (bg_BG)

[chennes]

For reference, here's mine:

Code: Select all

OS: Windows 10 Version 2009
Word size of FreeCAD: 64-bit
Version: 0.20.26700 +143 (Git)
Build type: Debug
Branch: addonManagerDependencyResolver
Hash: 28a25079e61bfb01acea9401228018544b45c82e
Python version: 3.8.6+
Qt version: 5.15.2
Coin version: 4.0.1
OCC version: 7.5.3
Locale: English/United States (en_US)

[Syres]

this is the result frome my local build which uses a recent 12.5.4. libpack downloaded from here https://github.com/apeltauer/FreeCAD/re ... ack_12.5.4
It strangely reports OCC as 7.5.0 and not 7.5 3.

If I saw something like that on my Linux platform (I compile against both OCC7.3 and 7.6 so I have to double check from time to time) I'd delete the CMakeCache.txt from my build folder and recompile but don't know if the same applies under Windows using a LibPack.

[sgrogan]

If I saw something like that on my Linux platform

For reference, here's mine:

Hey guys.
The root of the issue is that when we released 0.19.0/0.19.1 Uwe and I made some tweaks to apeltauer's 12.5.3 Libpack, and locally I named that 12.5.4.
Since then apeltauer posted a new Libpack with the same 12.5.4 name.

I'll update my scripts to use the new apeltauer 12.5.4 Libpack. In the future I'll use a convention like 12.5.4-s1 (i.e. -sgroganX) to avoid confusion.

Do you think its worth to add the SHA256 of the used Libpack to the SHA256.txt file for the build?

[chennes]

Do you think its worth to add the SHA256 of the used Libpack to the SHA256.txt file for the build?

Like, the hash of the Zip file from apeltauer's release page? Or calculated fresh from the on-disk files?

[kisolre]

I saw something like that on my Linux platform

Yes, something like that happened, I removed all older libpacks, downloaded again, cleared cmake cache, configure with all "copy" options ticked, generate and now rebuilding all. Will report if the warning is there if rebuild succeeds.