Message48798
The Visual Studio .NET vcproj files were probably
generated by importing the older Visual C++ 6.0 dsp
files and saving them back into the new format. The
convertor is not perfect. The bigest problem it has
it's the handling of the configuration macro defines.
Instead of defining the used macros once for each
configuration, it defines them for each individual
file. This causes file bloat and could cause problems
when new files are added to the project since we could
get builds with mixed defines due to the $(NoInherit)
flag which makes the compiler ignore global defines.
For example, the current pythoncore.vcproj file has 100
KB. A cleaned up version is less than 25 KB.
NOW:
<File
RelativePath="..\Parser\acceler.c">
<FileConfiguration
Name="Release|Win32">
<Tool
Name="VCCLCompilerTool"
Optimization="2"
AdditionalIncludeDirectories=""
PreprocessorDefinitions="NDEBUG;WIN32;_WINDOWS;USE_DL_EXPORT;$(NoInherit)"/>
</FileConfiguration>
<FileConfiguration
Name="Debug|Win32">
<Tool
Name="VCCLCompilerTool"
Optimization="0"
AdditionalIncludeDirectories=""
PreprocessorDefinitions="_DEBUG;USE_DL_EXPORT;WIN32;_WINDOWS;$(NoInherit)"/>
</FileConfiguration>
<FileConfiguration
Name="ReleaseItanium|Win32">
<Tool
Name="VCCLCompilerTool"
Optimization="2"
AdditionalIncludeDirectories=""
PreprocessorDefinitions="NDEBUG;WIN32;_WINDOWS;USE_DL_EXPORT;$(NoInherit)"/>
</FileConfiguration>
</File>
CLEANED-UP:
<File
RelativePath="..\Parser\acceler.c">
</File>
There are a couple of files which require custom options:
..\Modules\getbuildinfo.c -
PreprocessorDefinitions="BUILD=67"
..\PC\import_nt.c -
AdditionalIncludeDirectories="..\Python"
|
|
Date |
User |
Action |
Args |
2007-08-23 15:44:03 | admin | link | issue1307806 messages |
2007-08-23 15:44:03 | admin | create | |
|