Skip to content

C
cpython
Kaydet (Commit) 090c2161 authored tarafından Tim Peters's avatar Tim Peters
Dosyalara gözat
Seçenekler

The example_nt directory was old enough to vote. Frank Stajano 

pointed out some of the problems he had following the instructions,
and I stumbled into the others:  MSVC has changed in several
respects, Python has changed the directories into which it builds
its own Windows outputs, and we grew the unusual scheme of
appending "_d" to the names of debug-mode output files.

This should all work with VC6 + CVS Python now.  Some other Windows
geek please confirm!  And the less you know, the better <0.5 wink>.

Explanations and examples for versions of MSVC before 6, and
versions of Python before 2.0b1, have been removed, because
they're too different and so confuse life.  This last step I OK'ed
with Guido first (indeed, 'twas his idea!).
üst 019bcb59
Show whitespace changes
Inline Side-by-side
Showing with 134 additions and 401 deletions
PC/example_nt/example.dsp
Dosyayı görüntüle @ 090c2161
# Microsoft Developer Studio Project File - Name="example" - Package Owner=<4> # Microsoft Developer Studio Project File - Name="example" - Package Owner=<4>
# Microsoft Developer Studio Generated Build File, Format Version 5.00 # Microsoft Developer Studio Generated Build File, Format Version 6.00
# ** DO NOT EDIT ** # ** DO NOT EDIT **
# TARGTYPE "Win32 (x86) Dynamic-Link Library" 0x0102 # TARGTYPE "Win32 (x86) Dynamic-Link Library" 0x0102
...@@ -17,12 +17,12 @@ CFG=example - Win32 Release ...@@ -17,12 +17,12 @@ CFG=example - Win32 Release
!MESSAGE !MESSAGE
!MESSAGE Possible choices for configuration are: !MESSAGE Possible choices for configuration are:
!MESSAGE !MESSAGE
!MESSAGE "example - Win32 Release" (based on\ !MESSAGE "example - Win32 Release" (based on "Win32 (x86) Dynamic-Link Library")
"Win32 (x86) Dynamic-Link Library")
!MESSAGE "example - Win32 Debug" (based on "Win32 (x86) Dynamic-Link Library") !MESSAGE "example - Win32 Debug" (based on "Win32 (x86) Dynamic-Link Library")
!MESSAGE !MESSAGE
# Begin Project # Begin Project
# PROP AllowPerConfigDependencies 0
# PROP Scc_ProjName "" # PROP Scc_ProjName ""
# PROP Scc_LocalPath "" # PROP Scc_LocalPath ""
CPP=cl.exe CPP=cl.exe
...@@ -70,7 +70,7 @@ LINK32=link.exe ...@@ -70,7 +70,7 @@ LINK32=link.exe
# PROP Ignore_Export_Lib 0 # PROP Ignore_Export_Lib 0
# PROP Target_Dir "" # PROP Target_Dir ""
# ADD BASE CPP /nologo /MTd /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /c # ADD BASE CPP /nologo /MTd /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /c
# ADD CPP /nologo /MDd /W3 /Gm /GX /Zi /Od /I "..\Include" /I "..\PC" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /FD /c # ADD CPP /nologo /MDd /W3 /Gm /GX /ZI /Od /I "..\Include" /I "..\PC" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /FD /c
# ADD BASE MTL /nologo /D "_DEBUG" /win32 # ADD BASE MTL /nologo /D "_DEBUG" /win32
# ADD MTL /nologo /D "_DEBUG" /mktyplib203 /win32 # ADD MTL /nologo /D "_DEBUG" /mktyplib203 /win32
# ADD BASE RSC /l 0x409 /d "_DEBUG" # ADD BASE RSC /l 0x409 /d "_DEBUG"
......
PC/example_nt/example.dsw
Dosyayı görüntüle @ 090c2161
Microsoft Developer Studio Workspace File, Format Version 5.00 Microsoft Developer Studio Workspace File, Format Version 6.00
# WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE! # WARNING: DO NOT EDIT OR DELETE THIS WORKSPACE FILE!
############################################################################### ###############################################################################
Project: "example"=".\example.dsp" - Package Owner=<4> Project: "example"=.\example.dsp - Package Owner=<4>
Package=<5> Package=<5>
{{{ {{{
......
PC/example_nt/example.mak deleted 100644 → 0
Dosyayı görüntüle @ 019bcb59
# Microsoft Developer Studio Generated NMAKE File, Format Version 4.20
# ** DO NOT EDIT **
# TARGTYPE "Win32 (x86) Dynamic-Link Library" 0x0102
!IF "$(CFG)" == ""
CFG=example - Win32 Debug
!MESSAGE No configuration specified. Defaulting to example - Win32 Debug.
!ENDIF
!IF "$(CFG)" != "example - Win32 Release" && "$(CFG)" !=\
"example - Win32 Debug"
!MESSAGE Invalid configuration "$(CFG)" specified.
!MESSAGE You can specify a configuration when running NMAKE on this makefile
!MESSAGE by defining the macro CFG on the command line. For example:
!MESSAGE
!MESSAGE NMAKE /f "example.mak" CFG="example - Win32 Debug"
!MESSAGE
!MESSAGE Possible choices for configuration are:
!MESSAGE
!MESSAGE "example - Win32 Release" (based on\
"Win32 (x86) Dynamic-Link Library")
!MESSAGE "example - Win32 Debug" (based on "Win32 (x86) Dynamic-Link Library")
!MESSAGE
!ERROR An invalid configuration is specified.
!ENDIF
!IF "$(OS)" == "Windows_NT"
NULL=
!ELSE
NULL=nul
!ENDIF
################################################################################
# Begin Project
# PROP Target_Last_Scanned "example - Win32 Debug"
CPP=cl.exe
RSC=rc.exe
MTL=mktyplib.exe
!IF "$(CFG)" == "example - Win32 Release"
# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 0
# PROP BASE Output_Dir "Release"
# PROP BASE Intermediate_Dir "Release"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 0
# PROP Output_Dir "Release"
# PROP Intermediate_Dir "Release"
# PROP Target_Dir ""
OUTDIR=.\Release
INTDIR=.\Release
ALL : "$(OUTDIR)\example.dll"
CLEAN :
-@erase "$(INTDIR)\example.obj"
-@erase "$(OUTDIR)\example.dll"
-@erase "$(OUTDIR)\example.exp"
-@erase "$(OUTDIR)\example.lib"
"$(OUTDIR)" :
if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
# ADD BASE CPP /nologo /MT /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /YX /c
# ADD CPP /nologo /MD /W3 /GX /O2 /I "../Include" /I "../PC" /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /YX /c
CPP_PROJ=/nologo /MD /W3 /GX /O2 /I "../Include" /I "../PC" /D "WIN32" /D\
"NDEBUG" /D "_WINDOWS" /Fp"$(INTDIR)/example.pch" /YX /Fo"$(INTDIR)/" /c
CPP_OBJS=.\Release/
CPP_SBRS=.\.
# ADD BASE MTL /nologo /D "NDEBUG" /win32
# ADD MTL /nologo /D "NDEBUG" /win32
MTL_PROJ=/nologo /D "NDEBUG" /win32
# ADD BASE RSC /l 0x409 /d "NDEBUG"
# ADD RSC /l 0x409 /d "NDEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
BSC32_FLAGS=/nologo /o"$(OUTDIR)/example.bsc"
BSC32_SBRS= \
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /dll /machine:I386
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /dll /machine:I386
LINK32_FLAGS=kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib\
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib\
odbccp32.lib /nologo /subsystem:windows /dll /incremental:no\
/pdb:"$(OUTDIR)/example.pdb" /machine:I386 /def:".\example.def"\
/out:"$(OUTDIR)/example.dll" /implib:"$(OUTDIR)/example.lib"
DEF_FILE= \
".\example.def"
LINK32_OBJS= \
"$(INTDIR)\example.obj" \
"..\vc40\python15.lib"
"$(OUTDIR)\example.dll" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
$(LINK32) @<<
$(LINK32_FLAGS) $(LINK32_OBJS)
<<
!ELSEIF "$(CFG)" == "example - Win32 Debug"
# PROP BASE Use_MFC 0
# PROP BASE Use_Debug_Libraries 1
# PROP BASE Output_Dir "Debug"
# PROP BASE Intermediate_Dir "Debug"
# PROP BASE Target_Dir ""
# PROP Use_MFC 0
# PROP Use_Debug_Libraries 1
# PROP Output_Dir "Debug"
# PROP Intermediate_Dir "Debug"
# PROP Target_Dir ""
OUTDIR=.\Debug
INTDIR=.\Debug
ALL : "$(OUTDIR)\example.dll"
CLEAN :
-@erase "$(INTDIR)\example.obj"
-@erase "$(INTDIR)\vc40.idb"
-@erase "$(INTDIR)\vc40.pdb"
-@erase "$(OUTDIR)\example.dll"
-@erase "$(OUTDIR)\example.exp"
-@erase "$(OUTDIR)\example.ilk"
-@erase "$(OUTDIR)\example.lib"
-@erase "$(OUTDIR)\example.pdb"
"$(OUTDIR)" :
if not exist "$(OUTDIR)/$(NULL)" mkdir "$(OUTDIR)"
# ADD BASE CPP /nologo /MTd /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /c
# ADD CPP /nologo /MDd /W3 /Gm /GX /Zi /Od /I "../Include" /I "../PC" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /c
CPP_PROJ=/nologo /MDd /W3 /Gm /GX /Zi /Od /I "../Include" /I "../PC" /D "WIN32"\
/D "_DEBUG" /D "_WINDOWS" /Fp"$(INTDIR)/example.pch" /YX /Fo"$(INTDIR)/"\
/Fd"$(INTDIR)/" /c
CPP_OBJS=.\Debug/
CPP_SBRS=.\.
# ADD BASE MTL /nologo /D "_DEBUG" /win32
# ADD MTL /nologo /D "_DEBUG" /win32
MTL_PROJ=/nologo /D "_DEBUG" /win32
# ADD BASE RSC /l 0x409 /d "_DEBUG"
# ADD RSC /l 0x409 /d "_DEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
BSC32_FLAGS=/nologo /o"$(OUTDIR)/example.bsc"
BSC32_SBRS= \
LINK32=link.exe
# ADD BASE LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /dll /debug /machine:I386
# ADD LINK32 kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib /nologo /subsystem:windows /dll /debug /machine:I386
LINK32_FLAGS=kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib\
advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib\
odbccp32.lib /nologo /subsystem:windows /dll /incremental:yes\
/pdb:"$(OUTDIR)/example.pdb" /debug /machine:I386 /def:".\example.def"\
/out:"$(OUTDIR)/example.dll" /implib:"$(OUTDIR)/example.lib"
DEF_FILE= \
".\example.def"
LINK32_OBJS= \
"$(INTDIR)\example.obj" \
"..\vc40\python15.lib"
"$(OUTDIR)\example.dll" : "$(OUTDIR)" $(DEF_FILE) $(LINK32_OBJS)
$(LINK32) @<<
$(LINK32_FLAGS) $(LINK32_OBJS)
<<
!ENDIF
.c{$(CPP_OBJS)}.obj:
$(CPP) $(CPP_PROJ) $<
.cpp{$(CPP_OBJS)}.obj:
$(CPP) $(CPP_PROJ) $<
.cxx{$(CPP_OBJS)}.obj:
$(CPP) $(CPP_PROJ) $<
.c{$(CPP_SBRS)}.sbr:
$(CPP) $(CPP_PROJ) $<
.cpp{$(CPP_SBRS)}.sbr:
$(CPP) $(CPP_PROJ) $<
.cxx{$(CPP_SBRS)}.sbr:
$(CPP) $(CPP_PROJ) $<
################################################################################
# Begin Target
# Name "example - Win32 Release"
# Name "example - Win32 Debug"
!IF "$(CFG)" == "example - Win32 Release"
!ELSEIF "$(CFG)" == "example - Win32 Debug"
!ENDIF
################################################################################
# Begin Source File
SOURCE=.\example.c
DEP_CPP_EXAMP=\
"..\Include\abstract.h"\
"..\Include\ceval.h"\
"..\Include\classobject.h"\
"..\Include\cobject.h"\
"..\Include\complexobject.h"\
"..\Include\dictobject.h"\
"..\Include\fileobject.h"\
"..\Include\floatobject.h"\
"..\Include\funcobject.h"\
"..\Include\import.h"\
"..\Include\intobject.h"\
"..\Include\intrcheck.h"\
"..\Include\listobject.h"\
"..\Include\longobject.h"\
"..\Include\methodobject.h"\
"..\Include\modsupport.h"\
"..\Include\moduleobject.h"\
"..\Include\mymalloc.h"\
"..\Include\myproto.h"\
"..\Include\object.h"\
"..\Include\objimpl.h"\
"..\Include\pydebug.h"\
"..\Include\pyerrors.h"\
"..\Include\pyfpe.h"\
"..\Include\pystate.h"\
"..\Include\pythonrun.h"\
"..\Include\rangeobject.h"\
"..\Include\sliceobject.h"\
"..\Include\stringobject.h"\
"..\Include\sysmodule.h"\
"..\Include\traceback.h"\
"..\Include\tupleobject.h"\
".\../Include\Python.h"\
".\../PC\config.h"\
"$(INTDIR)\example.obj" : $(SOURCE) $(DEP_CPP_EXAMP) "$(INTDIR)"
# End Source File
################################################################################
# Begin Source File
SOURCE=.\readme.txt
!IF "$(CFG)" == "example - Win32 Release"
!ELSEIF "$(CFG)" == "example - Win32 Debug"
!ENDIF
# End Source File
################################################################################
# Begin Source File
SOURCE=.\example.def
!IF "$(CFG)" == "example - Win32 Release"
!ELSEIF "$(CFG)" == "example - Win32 Debug"
!ENDIF
# End Source File
################################################################################
# Begin Source File
SOURCE=\users\guido\python\src\vc40\python15.lib
!IF "$(CFG)" == "example - Win32 Release"
!ELSEIF "$(CFG)" == "example - Win32 Debug"
!ENDIF
# End Source File
# End Target
# End Project
################################################################################
PC/example_nt/readme.txt
Dosyayı görüntüle @ 090c2161
Example Python extension for Windows NT Example Python extension for Windows NT
======================================= =======================================
This directory contains everything you need to build a Python This directory contains everything needed (except for the Python
extension module using Microsoft VC++ ("Developer Studio") version 4.x distribution!) to build a Python extension module using Microsoft VC++
or 5.x, except for the Python distribution. It has been tested with ("Developer Studio") version 6. It has been tested with VC++ 6.0 on Python
VC++ 4.2 on Python 1.5a3, and with VC++ 5.0 on Python 1.5b2. 2.0b1. You can also use earlier versions of VC to build Python extensions,
but the sample VC project file (example.dsw in this directory) is in VC 6
The "example_nt" subdirectory should be an immediate subdirectory of format.
the Python source directory -- a direct sibling of Include and PC, in
particular, which are referenced as "..\Include" and "..\PC". In COPY THIS DIRECTORY!
other words, it should *not* be used "as is". Copy or move it up one --------------------
level or you will regret it! (This is done to keep all the PC This "example_nt" directory is a subdirectory of the PC directory, in order
specific files inside the PC subdirectory of the distribution, where to keep all the PC-specific files under the same directory. However, the
they belong.) example_nt directory can't actually be used from this location. You first
need to copy or move it up one level, so that example_nt is a direct
When using the VC++ 4.x project (makefile), it is assumed that the sibling of the PC\ and Include\ directories. Do all your work from within
build results of Python are in the directory ..\vc40. In particular, this new location -- sorry, but you'll be sorry if you don't.
the python15.lib file is referred to as "..\vc40\python15.lib". If
you have problems with this file, the best thing to do is to delete it OPEN THE PROJECT
from the project and add it again. ----------------
From VC 6.x, use the
When using the VC++ 5.x project (workspace), the build results of File -> Open Workspace...
Python are assumed to be in ..\PCbuild. Since the provided VC++ 5.x dialog (*not* the "File -> Open..." dialog!). Navigate to and select the
project and workspace files have a different structure (to support file "example.dsw". Click Open.
separate "release" and "debug" builds), the example project and
workspace match this structure. BUILD THE EXAMPLE DLL
---------------------
In order to use the example project from VC++ 4.x, use the "File->Open
Workspace..." dialog (*not* the "File->Open..." dialog!). Change the
pattern to "*.mak" and select the file "example.mak". Now choose
"File->Save All" and the othe project files will be created.
From VC+ 5.x, do the same except don't change the pattern, and select
the example.dsw workspace file.
In order to check that everything is set up right, try building: In order to check that everything is set up right, try building:
choose "Build->Build example.dll". This creates all intermediate and
result files in a subdirectory which is called either Debug or Release
depending on which configuration you have chosen.
Once the build has succeeded, test the resulting DLL. In a DOS 1. Select a configuration. This step is optional. Do
command window, chdir to that directory. You should now be able to Build -> Select Active Configuration...
repeat the following session "(C>" is the DOS prompt, ">>>" is the and select either "example - Win32 Release" or "example - Win32 Debug".
Python prompt): If you skip this step, you'll use the Debug configuration by default.
C> ..\..\vc40\python.exe 2. Build the DLL. Do
Build -> Build example_d.dll
in Debug mode, or
Build -> Build example.dll
in Release mode.
This creates all intermediate and result files in a subdirectory which
is called either Debug or Release, depending on which configuration you
picked in the preceding step.
TESTING THE DEBUG-MODE DLL
--------------------------
Once the Debug build has succeeded, bring up a DOS box, and cd to
example_nt\Debug. You should now be able to repeat the following session
("C>" is the DOS prompt, ">>>" is the Python prompt) (note that various
debug output from Python may not match this screen dump exactly):
C>..\..\PCbuild\python_d
Adding parser accelerators ...
Done.
Python 2.0b1 (#0, Jul 1 2000, 11:29:37) [MSC 32 bit (Intel)] on win32
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
Copyright 1995-2000 Corporation for National Research Initiatives (CNRI)
>>> import example >>> import example
[8830 refs]
>>> example.foo() >>> example.foo()
Hello, world Hello, world
[8830 refs]
>>> >>>
When using VC++ 5.x, issue these commands: TESTING THE RELEASE-MODE DLL
----------------------------
C> ..\..\PCbuild\Release\python.exe Once the Release build has succeeded, bring up a DOS box, and cd to
example_nt\Release. You should now be able to repeat the following session
("C>" is the DOS prompt, ">>>" is the Python prompt):
C>..\..\PCbuild\python
Python 2.0b1 (#0, Jul 1 2000, 11:28:35) [MSC 32 bit (Intel)] on win32
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
Copyright 1995-2000 Corporation for National Research Initiatives (CNRI)
>>> import example >>> import example
>>> example.foo() >>> example.foo()
Hello, world Hello, world
>>> >>>
Congratulations! You've successfully built your first Python extension
Creating the project module.
--------------------
CREATING YOUR OWN PROJECT
There are two ways to use this example to create a project for your -------------------------
own module. First, choose a name ("spam" is always a winner :-) and Choose a name ("spam" is always a winner :-) and create a directory for
create a directory for it. Copy your C sources into it. Note that it. Copy your C sources into it. Note that the module source file name
the module source file name does not necessarily have to match the does not necessarily have to match the module name, but the "init" function
module name, but the "init" function name should match the module name name should match the module name -- i.e. you can only import a module
-- i.e. you can only import a module "spam" if its init function is "spam" if its init function is called "initspam()", and it should call
called "initspam()", and it should call Py_InitModule with the string Py_InitModule with the string "spam" as its first argument (use the minimal
"spam" as its first argument. By convention, it lives in a file example.c in this directory as a guide). By convention, it lives in a file
called "spam.c" or "spammodule.c". The output file should be called called "spam.c" or "spammodule.c". The output file should be called
"spam.dll" or "spam.pyd" (the latter is supported to avoid confusion "spam.dll" or "spam.pyd" (the latter is supported to avoid confusion with a
with a system library "spam.dll" to which your module could be a system library "spam.dll" to which your module could be a Python interface)
Python interface). in Release mode, or spam_d.dll or spam_d.pyd in Debug mode.
Now your options are: Now your options are:
1) Clone example.mak. Start by copying example_nt\example.mak to 1) Copy example.dsw and example.dsp, rename them to spam.*, and edit them
spam\spam.mak. Do a global edit on spam.mak, replacing all by hand.
occurrences of the string "example" by "spam", and all occurrences of
"DEP_CPP_EXAMP" by something like "DEP_CPP_SPAM". You can now use or
this makefile to create a project file by opening it as a workspace
(you have to change the pattern to *.mak first). (When using VC++
5.x, you can clone example.dsp and example.dsw in a similar way.)
2) Create a brand new project; instructions are below. 2) Create a brand new project; instructions are below.
In both cases, copy example_nt\example.def to spam\spam.def, and edit In either case, copy example_nt\example.def to spam\spam.def, and edit the
spam\spam.def so its second line contains the string "initspam". If new spam.def so its second line contains the string "initspam". If you
you created a new project yourself, add the file spam.def to the created a new project yourself, add the file spam.def to the project now.
project now. (This is an annoying little file with only two lines. (This is an annoying little file with only two lines. An alternative
An alternative approach is to forget about the .def file, and add the approach is to forget about the .def file, and add the option
option "/export:initspam" somewhere to the Link settings, by manually "/export:initspam" somewhere to the Link settings, by manually editing the
editing the "Project Options" box). "Project Options" box).
You are now all set to build your extension, unless it requires other You are now all set to build your extension, unless it requires other
external libraries, include files, etc. See Python's Extending and external libraries, include files, etc. See Python's Extending and
Embedding manual for instructions on how to write an extension. Embedding manual for instructions on how to write an extension.
Creating a brand new project CREATING A BRAND NEW PROJECT
---------------------------- ----------------------------
Use the
If you don't feel comfortable with editing Makefiles or project and File -> New... -> Projects
workspace files, you can create a brand new project from scratch dialog to create a new Project Workspace. Select "Win32 Dynamic-Link
easily. Library", enter the name ("spam"), and make sure the "Location" is set to
the spam directory you have created (which should be a direct subdirectory
Use the "File->New..." dialog to create a new Project Workspace. of the Python build tree, a sibling of Inclue and PC). Select Win32 as the
Select Dynamic-Link Library, enter the name ("spam"), and make sure platform (in my version, this is the only choice). Make sure the "Create
the "Location" is set to the spam directory you have created (which new workspace" radio button is selected. Click OK.
should be a direct subdirectory of the Python build tree). Select
Win32 as the platform (in my version, this is the only choice). Click Now open the
"Create". Project -> Settings...
dialog. (Impressive, isn't it? :-) You only need to change a few
Now open the "Build->Settings..." dialog. (Impressive, isn't it? :-) settings. Make sure "All Configurations" is selected from the "Settings
You only need to change a few settings. Make sure you have both the for:" dropdown list. Select the "C/C++" tab. Choose the "Preprocessor"
Debug and the Release configuration selected when you make the first category in the popup menu at the top. Type the following text in the
change. Select the "C/C++" tab. Choose the "Preprocessor" category entry box labeled "Addditional include directories:"
in the popup menu at the top. Type the following text in the entry
box labeled "Addditional include directories:"
..\Include,..\PC ..\Include,..\PC
Next, for both configurations, select the "Link" tab, choose the Then, choose the "Input" category in the Link tab, and enter
"General" category, and add "python15.lib" to the end of the ..\PCbuild
"Object/library modules" box. in the "Additional library path:" box.
Now you need to add some mode-specific settings:
Then, separately for the Release and Debug configurations, choose the Select "Win32 Release" in the "Settings for:" dropdown list. Click the
"Input" category in the Link tab, and enter "..\PCbuild\Release" or "Link" tab, choose the "Input" Category, and append "python20.lib" to the
"..\PCbuild\Debug", respectively, in the "Additional library path" list in the "Object/library modules:" box.
box.
Finally, you must change the run-time library. This must also be done Select "Win32 Debug" in the "Settings for:" dropdown list, and append
separately for the Release and Debug configurations. Choose the "Code "python20_d.lib" to the list in the "Object/library modules:" box. Then
Generation" category in the C/C++ tab. In the box labeled "Use click on the C/C++ tab, select "Code Generation" from the "Category:"
run-time library", choose "Multithreaded DLL" for the Release dropdown list, and select "Debug Multithreaded DLL" from the "Use run-time
configuration, and "Debug Multithreaded DLL" for the Debug library:" dropdown list.
configuration. That's all.
You should now first create the file spam.def as instructed in the Select "Win32 Release" again from the "Settings for:" dropdown list.
previous section. Select "Multithreaded DLL" from the "Use run-time library:" dropdown list.
Now chose the "Insert->Files into Project..." dialog. Set the pattern That's all <wink>.
to *.* and select both spam.c and spam.def and click OK. (Inserting
them one by one is fine too.)
You should now create the file spam.def as instructed in the previous
section. Then chose the
Insert -> Files into Project...
dialog. Set the pattern to *.* and select both spam.c and spam.def and
click OK. (Inserting them one by one is fine too.)
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment