cmake on windows

[Sashan]

The OpenSSL installation on windows is not quite right with respect to cmake.

In order to investigate performance degradation on windows I had to build perftools using cmake.

There is no joy when one is trying cmake 4.2. My typical unix workflow is as follows:

# ./Configure --prefix=~/work.openssl/openssl.binaries/openssl-master
# make && make install
# cd ../perftools/source
# cmake -B build.master -S . -DCMAKE_PREFIX_PATH=~/work.openssl/openssl.binaries/openssl-master -DOPENSSL_CONFIG_MODE=1
# cmake --build build

Adjusting steps above for windows gives me no joy

# perl ./Configure --prefix=C:\Users\OpenSSL\work.openssl\openssl.binaries\openssl-master --openssldir=C:\Users\OpenSSL\work.openssl\openssl.binaries\openssl-master
# nmake
# nmake install
# cd ..
# cd perftools\source
# cmake -B build.master -S . -DCMAKE_PREFIX_PATH=~/work.openssl/openssl.binaries/openssl-master -DOPENSSL_CONFIG_MODE=1

The --openssldir option is needed so configuration files are not installed to its default under c:\Program Files...

For cmake 3.x one can adjust to configure step to point cmake to OpenSSL sources with fresh build. This is the desired command line:

cmake -B build.master -S . -DOPENSSL_ROOT_DIR=~/work.openssl/openssl.binaries/openssl-master

However the step above is completely futile with cmake 4.x No matter what I do cmake always complains for missing OpenSSLConfig.cmake or openssl-config.cmake

[levitte]

Can you show what's actually happening?

[levitte]

So, I had to try it on an Windows machine I've at home, that I haven't started for more than a year. It has cmake 3.26.3, which understands OPENSSL_CONFIG_MODE, so I ran with that. cmake build looked like this (with a fresh OpenSSL master built, and installed in C:\Users\Richard\Work\_openssl, and openssldir = C:\Users\Richard\Work\_openssl\etc):

$ cd perftools\source
$ cmake -B _build -S . -DCMAKE_PREFIX_PATH=C:\Users\Richard\Work\_openssl -DOPENSSL_CONFIG_MODE=1
...
$ cmake --build _build
...
$

Fine so far! But...

$ _build\radnbytes.exe 10

This got me en error dialog saying it can't find libcrypto-4.dll ... and yeah, that.

So, Windows basically requires the DLLs used by a program to reside in the same directory as the program (this is not the whole truth, but it's the easiest non-system solution). I thought that cmake had a knob to take care of that, or was even doing it automatically... but perhaps that's not quite true, I dunno.

Is this the "no joy" you experienced, or was yours something else?

I'll try with cmake 4.x next

[levitte]

No difference at all with cmake 4.2.3

[Sashan]

I'm still being puzzled why build with -DOPENSSL_ROOT_DIR=~/work.openssl/openssl.binaries/openssl-master option does not work on windows (at least for me)