• Suliman (15/15) Jan 28 2019 Does anybody have success with using vibed 0.8.4 with OpenSSL
• bauss (6/21) Jan 29 2019 Always compile vibe.d with mscoff
• Suliman (1/2) Jan 29 2019 Could you show command to compile with mscoff?
• Suliman (4/6) Jan 29 2019 I am not sure that all works fine, but at last I do not have
• Andre Pany (5/12) Jan 29 2019 Also you set the default architecture for dub as described here:
• Suliman (5/12) Jan 29 2019 Sorry, it was my mistake. I complied another project. Nothing do
• bauss (5/18) Jan 29 2019 Another way is just doing:

Suliman <evermind live.ru> writes:

Does anybody have success with using vibed 0.8.4 with OpenSSL 
1.0/1.1 on Windows?

I tried all possible solutions without any result. I am getting 
linking error:
Copyright (C) Digital Mars 1989-2013  All rights reserved.
http://www.digitalmars.com/ctg/optlink.html
C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _TLS_server_method
C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _TLS_client_method
C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _BN_get_rfc3526_prime_2048
C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _OPENSSL_init_ssl
Error: linker exited with status 4

bauss <jj_1337 live.dk> writes:

On Tuesday, 29 January 2019 at 06:48:38 UTC, Suliman wrote:
 Does anybody have success with using vibed 0.8.4 with OpenSSL 
 1.0/1.1 on Windows?

 I tried all possible solutions without any result. I am getting 
 linking error:
 Copyright (C) Digital Mars 1989-2013  All rights reserved.
 http://www.digitalmars.com/ctg/optlink.html
 C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _TLS_server_method
 C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _TLS_client_method
 C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _BN_get_rfc3526_prime_2048
 C:\Users\bubnenkov\AppData\Local\dub\packages\vibe-d-0.8.4\vibe-d\tls\.dub\build\openssl-release-windows-x86-dmd_2084-F1EDC8E792A20905C7802AF7FD58830B\vibe-d_tls.lib(openssl)
  Error 42: Symbol Undefined _OPENSSL_init_ssl
 Error: linker exited with status 4

Always compile vibe.d with mscoff

Not sure if that has anything to do with this linking error 
though.

I use vibe.d exclusively on Windows though and have had no 
problems.

Suliman <evermind live.ru> writes:

 Always compile vibe.d with mscoff

Could you show command to compile with mscoff?

Suliman <evermind live.ru> writes:

On Tuesday, 29 January 2019 at 10:01:04 UTC, Suliman wrote:
 Always compile vibe.d with mscoff

 Could you show command to compile with mscoff?

I am not sure that all works fine, but at last I do not have 
linking error. I have add to dub.sdl ext string:
"dflags-windows-x86": ["-m32mscoff"]

Andre Pany <andre s-e-a-p.de> writes:

On Tuesday, 29 January 2019 at 10:06:43 UTC, Suliman wrote:
 On Tuesday, 29 January 2019 at 10:01:04 UTC, Suliman wrote:
 Always compile vibe.d with mscoff

 Could you show command to compile with mscoff?

 I am not sure that all works fine, but at last I do not have 
 linking error. I have add to dub.sdl ext string:
 "dflags-windows-x86": ["-m32mscoff"]

Also you set the default architecture for dub as described here:
https://dub.pm/settings.html

Kind regards
Andre

Suliman <evermind live.ru> writes:

On Tuesday, 29 January 2019 at 10:06:43 UTC, Suliman wrote:
 On Tuesday, 29 January 2019 at 10:01:04 UTC, Suliman wrote:
 Always compile vibe.d with mscoff

 Could you show command to compile with mscoff?

 I am not sure that all works fine, but at last I do not have 
 linking error. I have add to dub.sdl ext string:
 "dflags-windows-x86": ["-m32mscoff"]

Sorry, it was my mistake. I complied another project. Nothing do 
not working correct string is:
dflags-windows-x86 "-m32mscoff"

But I got again linking problem.

bauss <jj_1337 live.dk> writes:

On Tuesday, 29 January 2019 at 10:12:30 UTC, Suliman wrote:
 On Tuesday, 29 January 2019 at 10:06:43 UTC, Suliman wrote:
 On Tuesday, 29 January 2019 at 10:01:04 UTC, Suliman wrote:
 Always compile vibe.d with mscoff

 Could you show command to compile with mscoff?

 I am not sure that all works fine, but at last I do not have 
 linking error. I have add to dub.sdl ext string:
 "dflags-windows-x86": ["-m32mscoff"]

 Sorry, it was my mistake. I complied another project. Nothing 
 do not working correct string is:
 dflags-windows-x86 "-m32mscoff"

 But I got again linking problem.

Another way is just doing:

dub -a=x86_mscoff

But uhmm not sure about the linking error. I will try locally 
later and see if I can reproduce it.