mirrors/cpython
mirrors/cpython
0
0
Fork 0
mirror of https://github.com/python/cpython.git synced 2024-11-24 17:47:13 +01:00
Code Issues Releases Activity
a2bf2709b3
cpython/PC/example_nt/example.dsp

118 lines
4.2 KiB
Plaintext
Raw Normal View History

Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
# Microsoft Developer Studio Project File - Name="example" - Package Owner=<4>
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!).
2000-07-03 01:18:43 +02:00
# Microsoft Developer Studio Generated Build File, Format Version 6.00
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
# ** DO NOT EDIT **
# TARGTYPE "Win32 (x86) Dynamic-Link Library" 0x0102
CFG=example - Win32 Release
!MESSAGE This is not a valid makefile. To build this project using NMAKE,
!MESSAGE use the Export Makefile command and run
!MESSAGE
!MESSAGE NMAKE /f "example.mak".
!MESSAGE
!MESSAGE You can specify a configuration when running NMAKE
!MESSAGE by defining the macro CFG on the command line. For example:
!MESSAGE
!MESSAGE NMAKE /f "example.mak" CFG="example - Win32 Release"
!MESSAGE
!MESSAGE Possible choices for configuration are:
!MESSAGE
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!).
2000-07-03 01:18:43 +02:00
!MESSAGE "example - Win32 Release" (based on "Win32 (x86) Dynamic-Link Library")
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
!MESSAGE "example - Win32 Debug" (based on "Win32 (x86) Dynamic-Link Library")
!MESSAGE
# Begin Project
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!).
2000-07-03 01:18:43 +02:00
# PROP AllowPerConfigDependencies 0
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
# PROP Scc_ProjName ""
# PROP Scc_LocalPath ""
CPP=cl.exe
MTL=midl.exe
RSC=rc.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 Ignore_Export_Lib 0
# PROP Target_Dir ""
# 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 /FD /c
# ADD BASE MTL /nologo /D "NDEBUG" /win32
# ADD MTL /nologo /D "NDEBUG" /mktyplib203 /win32
# ADD BASE RSC /l 0x409 /d "NDEBUG"
# ADD RSC /l 0x409 /d "NDEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
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
Update the example DLL instructions for 2.1. Add example.def to the MSVC project file (as the instructions always recommended doing).
2001-01-19 09:45:48 +01:00
# 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 python21.lib /nologo /subsystem:windows /dll /machine:I386 /libpath:"..\PCbuild" /export:initexample
update the example without the example.def file
1997-12-11 05:06:04 +01:00
# SUBTRACT LINK32 /pdb:none
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
!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 Ignore_Export_Lib 0
# PROP Target_Dir ""
# ADD BASE CPP /nologo /MTd /W3 /Gm /GX /Zi /Od /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /c
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!).
2000-07-03 01:18:43 +02:00
# ADD CPP /nologo /MDd /W3 /Gm /GX /ZI /Od /I "..\Include" /I "..\PC" /D "WIN32" /D "_DEBUG" /D "_WINDOWS" /YX /FD /c
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
# ADD BASE MTL /nologo /D "_DEBUG" /win32
# ADD MTL /nologo /D "_DEBUG" /mktyplib203 /win32
# ADD BASE RSC /l 0x409 /d "_DEBUG"
# ADD RSC /l 0x409 /d "_DEBUG"
BSC32=bscmake.exe
# ADD BASE BSC32 /nologo
# ADD BSC32 /nologo
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
Update the example DLL instructions for 2.1. Add example.def to the MSVC project file (as the instructions always recommended doing).
2001-01-19 09:45:48 +01:00
# 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 python21_d.lib /nologo /subsystem:windows /dll /debug /machine:I386 /out:".\Debug/example_d.dll" /libpath:"..\PCbuild" /export:initexample
update the example without the example.def file
1997-12-11 05:06:04 +01:00
# SUBTRACT LINK32 /pdb:none
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
!ENDIF
# Begin Target
# Name "example - Win32 Release"
# Name "example - Win32 Debug"
# Begin Group "Source Files"
# PROP Default_Filter "cpp;c;cxx;rc;def;r;odl;hpj;bat;for;f90"
# Begin Source File
SOURCE=.\example.c
# End Source File
# Begin Source File
Update the example DLL instructions for 2.1. Add example.def to the MSVC project file (as the instructions always recommended doing).
2001-01-19 09:45:48 +01:00
SOURCE=.\example.def
# End Source File
# Begin Source File
Adding VC 5.x workspace and project files
1997-12-11 04:43:29 +01:00
SOURCE=.\readme.txt
# End Source File
# End Group
# Begin Group "Header Files"
# PROP Default_Filter "h;hpp;hxx;hm;inl;fi;fd"
# End Group
# Begin Group "Resource Files"
# PROP Default_Filter "ico;cur;bmp;dlg;rc2;rct;bin;cnt;rtf;gif;jpg;jpeg;jpe"
# End Group
# End Target
# End Project
Copy Permalink