[Python-bugs-list] [ python-Bugs-505628 ] Bad instructions in readme file.
noreply@sourceforge.net
noreply@sourceforge.net
Fri, 18 Jan 2002 19:12:09 -0800
Bugs item #505628, was opened at 2002-01-18 19:12
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=505628&group_id=5470
Category: Documentation
Group: Python 2.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Martin Miller (mrmiller)
Assigned to: Fred L. Drake, Jr. (fdrake)
Summary: Bad instructions in readme file.
Initial Comment:
The directions in the ...\PC\example_nt\readme.txt in the section titled "CREATING A BRAND NEW
PROJECT" says:
> Select "Win32 Release" in the "Settings for:" dropdown list. Click the
> "Link" tab, choose the "Input" Category, and append "python21.lib" to the
> list in the "Object/library modules:" box.
Which is not true (any more?) because of a #pragma now in the ...\PC\Config.h file. Namely:
> #if !defined(USE_DL_EXPORT) && defined(_MSC_VER)
> /* So nobody using MSVC needs to specify the .lib in their Makefile any
> more (other compilers will still need to do so, but that's taken care
> of by the Distutils, so it's not a problem). */
> #ifdef _DEBUG
> #pragma comment(lib,"python21_d.lib")
> #else
> #pragma comment(lib,"python21.lib")
> #endif
> #endif /* USE_DL_EXPORT */
Personally I don't care for the #pragma technique -- it's too implicit and compiler specific. If
nothing else perhaps the paragraphi in the readme file could be replaced with a mention of how the
use of the pragma.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=505628&group_id=5470