[SERVER-23248] Building MongoDB server in Windows with static OpenSSL lib? Created: 20/Mar/16  Updated: 28/Mar/16  Resolved: 28/Mar/16

Status: Closed
Project: Core Server
Component/s: Build
Affects Version/s: 3.2.4
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Rex Conn Assignee: Andrew Morrow (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Platforms 12 (04/01/16)
Participants:

 Description   

Is it possible to build mongo.exe / mongod.exe in Windows with a static link to the openssl libs? When I try I with an openssl build using a static libeay32.lib & ssleay32.lib, I get an error from scons "Couldn't find OpenSSL ssl.h header and library").

Building mongo with the same openssl directory built with a dynamic libeay32.dll & .lib and ssleay32.dll & .lib works. But I would prefer to use the staticly linked openssl.

My scons build line looks like this:

scons MSVC_VERSION=12.0 --ssl CPPPATH=s:\sdk\openssl-1.0.2e-VS2013\include LIBPATH=s:\sdk\openssl-1.0.2e-VS2013\win64\lib --release --win-version-min=win7 all



 Comments   
Comment by Andrew Morrow (Inactive) [ 28/Mar/16 ]

Hi rconn - I'm closing this issue since we have not heard back from you with any additional details. Please feel free to re-open the ticket or comment on it if there is anything further we can do to help.

Comment by Andrew Morrow (Inactive) [ 23/Mar/16 ]

Can you provide a directory listing for the include and lib directories in each of the two different OpenSSL builds (static vs dynamic)? Could you also attach the contents of the file build/scons/config.log for each build, once against the dynamic and once against the static OpenSSL libraries? You will probably want to build with --config=force each time, to ensure that SCons re-runs each configure check rather than relying on cached values so that the config.log file is informative.

Generated at Thu Feb 08 04:02:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.