[cmake-developers] [CMake 0015071]: building cmake on Windows against statically compiled openssl puts dlls into bin directory

Mantis Bug Tracker mantis at public.kitware.com
Fri Aug 8 11:47:18 EDT 2014


The following issue has been SUBMITTED. 
====================================================================== 
http://www.cmake.org/Bug/view.php?id=15071 
====================================================================== 
Reported By:                Frank Benkstein
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   15071
Category:                   CMake
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2014-08-08 11:47 EDT
Last Modified:              2014-08-08 11:47 EDT
====================================================================== 
Summary:                    building cmake on Windows against statically
compiled openssl puts dlls into bin directory
Description: 
I am building a custom version of cmake 3.0.1 with 32bit Visual Studio 2010 on
64bit Windows 7.  In my build script I build openssl statically and then build
cmake with an installed version 3.0.0.

It seems that cmake builds and links correctly agaist my own openssl. 
Unfortunately, the libea32.dll and ssleay32.dll from the locally installed cmake
are also picked up and put into the install prefix.

I tracked this down to these rules in my ninja file:

# =============================================================================
# Write statements declared in CMakeLists.txt:
# C:/Users/Frank/Projects/custom-cmake/cmake/src/Utilities/cmcurl/CMakeLists.txt
# =============================================================================

<-- snip -->

#############################################
# Custom command for bin\.\libeay32.dll

build bin\.\libeay32.dll: CUSTOM_COMMAND C$:\usr\CMake-3.0.0\bin\libeay32.dll ||
Utilities\cmzlib\cmzlib.lib
  COMMAND = cmd.exe /C "cd /D
C:\Users\Frank\Projects\custom-cmake\cmake\gen\cmake-build\Utilities\cmcurl &&
C:\usr\CMake-3.0.0\bin\cmake.exe -E copy C:/usr/CMake-3.0.0/bin/libeay32.dll
C:/Users/Frank/Projects/custom-cmake/cmake/gen/cmake-build/bin/./libeay32.dll"
  DESC = Generating ../../bin/./libeay32.dll

#############################################
# Custom command for bin\.\ssleay32.dll

build bin\.\ssleay32.dll: CUSTOM_COMMAND C$:\usr\CMake-3.0.0\bin\ssleay32.dll ||
Utilities\cmzlib\cmzlib.lib
  COMMAND = cmd.exe /C "cd /D
C:\Users\Frank\Projects\custom-cmake\cmake\gen\cmake-build\Utilities\cmcurl &&
C:\usr\CMake-3.0.0\bin\cmake.exe -E copy C:/usr/CMake-3.0.0/bin/ssleay32.dll
C:/Users/Frank/Projects/custom-cmake/cmake/gen/cmake-build/bin/./ssleay32.dll"
  DESC = Generating ../../bin/./ssleay32.dll

I found the responsible code block in Utilities/cmcurl/CMakeLists.txt but I have
no idea how to fix it myself.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2014-08-08 11:47 Frank BenksteinNew Issue                                    
======================================================================



More information about the cmake-developers mailing list