Oh yes, you're right, the SqueakSLL could have been built but was not built in pharo... I just changed https://github.com/OpenSmalltalk/opensmalltalk-vm/edit/Cog/build.win64x64/ph... this should trigger another automated build and if all goes well you will have a new bintray artefact to test. 2017-11-06 10:21 GMT+01:00 Raffaello Giulietti < raffaello.giulietti@lifeware.ch>:
Hi Nicolas,
I tried both the vm found at the location you mention (dated 2017-10-22):
https://bintray.com/opensmalltalk/vm/download_file?file_ path=cog_win64x64_pharo.cog.spur_201710221351.zip
and the "official" latest vm on the Pharo site (dated 2017-11-01)
http://files.pharo.org/vm/pharo-spur64/win/pharo-win-x86_64- 201711010928-e14fbab.zip
Neither of them contains the SqueakSSL.dll and, in fact, in both cases I get an exception when using Gofer to download Roassal2, using the latest 60519 image:
Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadDevelopment
This works on Pharo 32 bit/Win, where SquekSSL is present.
On 2017-11-04 23:31, Nicolas Cellier wrote:
Note that win64 SSL works at least since https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/baa 70862014d3bb510f2edf7465e857c645be0e4 and https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/caa 8241de11b99ecaea5236b3d3e3c0d303c6eb4
Maybe it's a bit too recent to be found in official Pharo distribution, but if you can live with bleeding edge, pick a more recent VM here: https://bintray.com/opensmalltalk/vm/cog/201710221351#files (or maybe you can find one from the Pharo site?)
2017-11-04 22:21 GMT+01:00 henry <henry@callistohouse.club <mailto: henry@callistohouse.club>>:
This is the advantage of in-image SSL solution, found in the Cryptography repository:
http://www.squeaksource.com/Cryptography.html <http://www.squeaksource.com/Cryptography.html>
Sent from ProtonMail Mobile
On Fri, Nov 3, 2017 at 12:53, Raffaello Giulietti <raffaello.giulietti@lifeware.ch <mailto:raffaello.giulietti@lifeware.ch>> wrote:
Hi, the SqueakSSL dll is not included in the Pharo 64bit/Win vm distribution. I guess this has to do with problems in building it. Anybody knows where the difficulties lie? Greetings Raffaello