Difference in binary outputs in openssl package between Linux and Windows

[wesSTILMAN]

We have observed a difference between the build artifacts produced for the openssl package between Linux and Windows. On windows, someone may type:

c:\vcpkg>vcpkg install openssl

And in this location:

C:\vcpkg\installed\x64-windows\tools\openssl

The following artifacts will be seen:
openssl.exe
libcrypto-3-x64.dll
libssl-3-x64.dll

But on Linux, running:

./vcpkg install openssl

Does not even create an openssl folder in installed/x64-linux/tools.

Searching the entire drive I only see the openssl executable put there by the system repo manager. Is there a reason these things are not build on Linux?

Operating systems used: Windows 10 22H2, and RedHat 8 ( Linux 4.18.0-425.3.1.el8.x86_64).

[dg0yt]

Would this help? #27261

My x64-linux installation has:

$ find installed/x64-linux/tools/openssl
installed/x64-linux/tools/openssl
installed/x64-linux/tools/openssl/openssl
installed/x64-linux/tools/openssl/c_rehash

[wesSTILMAN]

Would this help? #27261

My x64-linux installation has:

$ find installed/x64-linux/tools/openssl
installed/x64-linux/tools/openssl
installed/x64-linux/tools/openssl/openssl
installed/x64-linux/tools/openssl/c_rehash

Indeed this does seem to help. The unified configuration also makes it much easier for us to synchronize instructions between platforms. Already, we have been able to confirm creation of the openssl executable using this PR. We have added enable-fips to CONFIGURE_OPTIONS and are currently trying to get that working, which was also failing in the trunk.

[MonicaLiu0311]

#27261 has been merged, if it is still an issue, please reopen this issue.

[wesSTILMAN]

We are still using the PR, but it all works very well. I’m glad this got merged in. Wes From: MonicaLiu ***@***.***> Sent: Thursday, April 20, 2023 4:10 AM To: microsoft/vcpkg ***@***.***> Cc: Wes Keene ***@***.***>; Mention ***@***.***> Subject: Re: [microsoft/vcpkg] Difference in binary outputs in openssl package between Linux and Windows (Issue #29400) @wesSTILMAN<https://github.com/wesSTILMAN> #27261<#27261> has been merged, has your problem been resolved? — Reply to this email directly, view it on GitHub<#29400 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AYSLCULGS2NPN3LXOH7TUSLXCDVONANCNFSM6AAAAAAUPPBSAA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[dg0yt]

FYI FIPS support is coming: #30916