Hi,
It unfortunately took a long time that I was able to check the problem below
again. The proposed fix is incorrect. Because the .mak file is generated by
util/mk1mf.pl, the change should be done on top of that file. Both for
openssl1.0.1e as well as for openssl1.0.1g the following diff can be applied
and adds a line to copy the pdb file to the lib directory.
Diff on <openSSLDir>/<opensslversion>/util/mk1mf.pl between original file and
changed file:
580c580,581
< \$(CP) \"\$(BIN_D)$o\$(E_EXE)$exep \$(INSTALLTOP)${o}bin\"
---
> \$(CP) \"\$(BIN_D)${o}\$(E_EXE)$exep \$(INSTALLTOP)${o}bin\"
> \$(CP) \"\$(OBJ_D)${o}lib.pdb\" \"\$(INSTALLTOP)${o}lib\"
I also replaced one occurrence of $o by ${o}, which means the same, but
semantically more adheres to what is already used.
The change is of minor importance, but just simplifies adoption by a Visual
Studio/Windows build (and solves warnings).
I assume that the name 'lib.pdb' is fixed, since I did not see a macro that
defines this name.
Regards,
Kees
-----Original Message-----
From: The default queue via RT [mailto:r...@openssl.org]
Sent: Thursday, September 26, 2013 19:08
To: Kees Dekker
Subject: [openssl.org #3133] AutoReply: minor make install improvement for
Windows/Visual Studio in ms\nt.mak
Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"minor make install improvement for Windows/Visual Studio in
ms\nt.mak",
a summary of which appears below.
There is no need to reply to this message right now. Your ticket has been
assigned an ID of [openssl.org #3133].
Please include the string:
[openssl.org #3133]
in the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
Thank you,
r...@openssl.org
-------------------------------------------------------------------------
Hi,
It may be useful to add the .pdb file to the lib directory in the install
target. Windows build that adopt OpenSSL may benefit from it. When using
ssleay32.lib and/or libeay32.lib then Visual Studio may complain about missing
symbol information. That information is in the pdb file. If a pdb file is not
provided, then Visual Studio will raise the following warning:
libeay32.lib(cryptlib.obj) : warning LNK4099: PDB 'lib.pdb' was not found with
'libeay32.lib(cryptlib.obj)' or at 'xyz\lib.pdb'; linking object as if no debug
info.
Suggestion: change ms\nt.mak a little and add a line, similar to the following
diff:
474c474
<
---
> $(CP) "$(OBJ_D)\lib.pdb" "$(INSTALLTOP)\lib"
Regards,
Kees Dekker
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager majord...@openssl.org
