Hi Alan, I have updated two Wiki pages to describe the issue. I hope I have provided enough details so that others will understand it. So, if someone can review this, that would be great.
The code you quoted is exactly what brings the dependency of python27_d.lib into the Python bindings for a Debug build with the MS Visual C/C++ compiler. And only in that particular combination! Code in the CMake FindPython module is related to this specific handling. Regards, Arjen > > Please go ahead and do that. I think the wiki is the >right place. > But please be really specific so others know exactly >what > happened to you and how to avoid that situation. We >want to > avoid the situation where Windows users who want to try > Python are discouraged from doing that because you >haven't > given enough specifics about the cause of the problem. > > To help you get started with being specific please state >that the issue is > due to the following section of pyconfig.h > > /* For an MSVC DLL, we can nominate the .lib files used >by extensions */ > #ifdef MS_COREDLL > # ifndef Py_BUILD_CORE /* not building the core - >must be an ext */ > # if defined(_MSC_VER) > /* So MSVC users need not >specify the .lib file in > their Makefile (other compilers >are generally > taken care of by distutils.) */ > # ifdef _DEBUG > # pragma >comment(lib,"python27_d.lib") > # else > # pragma >comment(lib,"python27.lib") > # endif /* _DEBUG */ > # endif /* _MSC_VER */ > # endif /* Py_BUILD_CORE */ > #endif /* MS_COREDLL */ > > The above was in pyconfig.h that I downloaded from the >official > Windows source at > http://www.python.org/ftp/python/2.7.1/python-2.7.1.msi >which I > subsequently installed (under Wine) using > > msiexec /i python-2.7.1.msi. > > You should also state the details of where you got >Python so users > know that the above code fragment comes from the >official Python > source for Windows. > > I assume the above section of pyconfig.h is the source >of the general > issue. But what was the specific thing wrong on your >platform? Was > it that you had #defined _DEBUG? Or does CMake do that >for some > configurations? Certainly when running cmake.exe in a >default way > under wine, I did not run into this issue, but I (and >other successful > Python users on Windows) will not know why everything >just worked for > us unless you are specific about what was wrong with >your approach. > 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. ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 _______________________________________________ Plplot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/plplot-devel
