From: Phil R. <p.d...@gm...> - 2016-05-24 08:18:53
|
Hi Arjen I see the same problem. 64 bit windows, 64 bit tcl, linking fails in visual studio for 32 bit builds. This is the only library I see this problem with, but I think I built all other dependencies myself, whereas I installed tcl with its installer. My solution is that I have just stopped doing 32 bit builds, but I appreciate there are still a few 32 bit windows installs around that you may need to compile for. For a while I persisted with a separate 32 bit cmake call, which I needed to do anyway to pull in the correct wxWidgets library. I just disabled tcl in that build. Phil -----Original Message----- From: "Arjen Markus" <Arj...@de...> Sent: 24/05/2016 07:48 To: "plp...@li..." <plp...@li...> Subject: [Plplot-devel] Distinction between 32-bits and 64-bits libraries Hello, Yesterday, while trying to solve an issue with the Tcl binding under bare Windows, I came across the following problem: - I have a 64-bits Tcl version installed - I use the 32-bits compiler environment (MS Visual Studio, set for 32 bits) - CMake finds the Tcl libraries and arranges for the Tcl bindings to be built - The build subsequently fails because the import library that is used (64-bits) is not suitable for the compilation and linking (32-bits) I presume similar things may happen with other external dependencies that come in different varieties. Should we guard against this happening or not? I have no idea how difficult it is to implement that. For now, I suggest we warn about the possibility of this confusion in the documentation. Regards, Arjen DISCLAIMER: This message is intended exclusively for the addressee(s) and may contain confidential and privileged information. If you are not the intended recipient please notify the sender immediately and destroy this message. Unauthorized use, disclosure or copying of this message is strictly prohibited. The foundation 'Stichting Deltares', which has its seat at Delft, The Netherlands, Commercial Registration Number 41146461, is not liable in any way whatsoever for consequences and/or damages resulting from the improper, incomplete and untimely dispatch, receipt and/or content of this e-mail. |