Visual C++6.0下的workspace和project结构初探 -VC6的dsp和dsw文件分析 最近下载Apache的httpd源码进行编译,使用VC6打开Apache.dsw以后进行编译,发现apr.h文件没有包含在下载的源码中,但编译后却发现存在该文件,为弄明白是何处产生arp.h文件,便阅读了Apache.dsp和Makefile.win等文件,整理和总结了apache的project组织结构和VC6下的Project组织结构。我会把文章中用到的apache文件都添加进来,使得大家不用下载apache源码,如果大家对apache编译有兴趣,可以参考我的另一篇文章:http://blog.csdn.net/ftomorrow/archive/2009/03/11/3980143.aspx。
一、Workspace中Projects的组织 用VC6打开Apache.dsw 以后,发现workspace包含许多的Projects:Apache、ApacheMonitor和libapr等。从网上搜到dsw文件的说明:dsw的全称是Developer Studio Workspace,属于最高级别的配置文件,记录了整个Workspace的配置信息,它是一个纯文本文件,通常在VC6创建新项目时自动生成。为弄明白VC中Project如何组织的,用文本编辑器打开Apache.dsw文件,发现其内容如下:
- Project: "Apache"="./Apache.dsp" - Package Owner=<4>
- Package=<5>
- {{{
- }}}
- Package=<4>
- {{{
- Begin Project Dependency
- Project_Dep_Name libapr
- End Project Dependency
- Begin Project Dependency
- Project_Dep_Name libaprutil
- End Project Dependency
- Begin Project Dependency
- Project_Dep_Name libhttpd
- End Project Dependency
- }}}
- ###############################################################################
- #此处省略许多Project,只以libapr为例说明
- #.....
- ###############################################################################
- Project: "libapr"="./srclib/apr/libapr.dsp" - Package Owner=<4>
- Package=<5>
- {{{
- }}}
- Package=<4>
- {{{
- }}}
- #
- #后续省略许多Project,只以libapr为例说明
- #.....
为了分析和研究dsw文件的格式,我用VC6建立新建一个名字为yang的项目,并添加一个main.cpp文件到该工程中,之后VC6自动生成了Project的项目文件 :yang.dsw和yang.dsp文件,打开yang.dsw文件,其内容如下:
- Project: "yang"=./yang.dsp - Package Owner=<4>
- Package=<5>
- {{{
- }}}
- Package=<4>
- {{{
- }}}
- Global:
- Package=<5>
- {{{
- }}}
- Package=<3>
- {{{
- }}}
- ###############################################################################
对比yang.dsw和apache.dsw格式,便可以发现dsw文件中包含两类Entry:Project和Global。一个dsw文件中可以包含多个Porect Entry(我不知Entry表述是否准确,但我没搜索到dsw文件格式说明,故采用Entry一说),如果包含了多个Project Entry说明该Workspace中含有多个Projects。每一个Project Entry开头为:
- Project:"yang"=./yang.dsp - Package Owner=<4>
其中yang是指project名字,每一个Project包含两个Package:Package=<5>和Package=<4>,如果同一个workspace中的多个Project之间有依赖关系,则会在Package=<4>中进行描述,如Apache.dsw中的Apache project的其中一个依赖关系定义为:
- Begin Project Dependency
- Project_Dep_Name libapr
- End Project Dependency
这表示Apache project依赖于libapr project,每一个project可以依赖于多个project,yang.dsw中因为只有yang一个project,所没有依赖关系。VC中可以通过Project->Dependencies菜单来修改和增加Project的依赖关系。 为验证以上分析是否正确,我把yang.dsp拷贝一份为zhang.dsp,然后把zhang.dsp中所有字符串yang替换成zhang,之后修改yang.dsw,在yang project section之后添
- ###############################################################################
- Project: "zhang"=./zhang.dsp - Package Owner=<4>
- Package=<5>
- {{{
- }}}
- Package=<4>
- {{{
- }}}
保存后使用VC6打开yang.dsw文件,便看到yang workspace中包含yang和zhang两个project。 二、Workspace中Project的编译 Apache手册中说:在windows下编译需要设置BuildBin project为Active project,然后进行编译(编译过程可以参考我的另外一篇文章:http://blog.csdn.net/ftomorrow/archive/2009/03/11/3980143.aspx)。既然设置了BuildBin project作为active project进行编译,其关键在于BuildBin.dsw 和BuildBin.dsp文件组织上。从网上搜到的dsp文件说明为:dsp全称是Developer Studio Project,是一个配置文件,它记录的是一个项目的所有配置信息,纯文本文件,主要用于配置编译。打开BuildBin.dsp文件,可以看到:
- # Microsoft Developer Studio Project File - Name="BuildBin" - Package Owner=<4>
- # Microsoft Developer Studio Generated Build File, Format Version 6.00
- # ** DO NOT EDIT **
- # TARGTYPE "Win32 (x86) External Target" 0x0106
- CFG=BuildBin - Win32 Debug
- !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 "BuildBin.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 "BuildBin.mak" CFG="BuildBin - Win32 Debug"
- !MESSAGE
- !MESSAGE Possible choices for configuration are:
- !MESSAGE
- !MESSAGE "BuildBin - Win32 Release" (based on "Win32 (x86) External Target")
- !MESSAGE "BuildBin - Win32 Debug" (based on "Win32 (x86) External Target")
- !MESSAGE
- # Begin Project
- # PROP AllowPerConfigDependencies 0
- # PROP Scc_ProjName ""
- # PROP Scc_LocalPath ""
- !IF "$(CFG)" == "BuildBin - Win32 Release"
- # PROP BASE Use_Debug_Libraries 0
- # PROP BASE Output_Dir ""
- # PROP BASE Intermediate_Dir ""
- # PROP BASE Cmd_Line "NMAKE /f makefile.win"
- # PROP BASE Rebuild_Opt "/a"
- # PROP BASE Target_File "/Apache2.0/bin/Apache.exe"
- # PROP BASE Bsc_Name "./Browse/BuildBin.bsc"
- # PROP BASE Target_Dir ""
- # PROP Use_Debug_Libraries 0
- # PROP Output_Dir ""
- # PROP Intermediate_Dir ""
- # PROP Cmd_Line "NMAKE /f makefile.win INSTDIR="/Apache2" LONG=Release _tryssl _tryzlib _dummy"
- # PROP Rebuild_Opt ""
- # PROP Target_File "/Apache2/bin/Apache.exe"
- # PROP Bsc_Name "./Browse/Apache.bsc"
- # PROP Target_Dir ""
- !ELSEIF "$(CFG)" == "BuildBin - Win32 Debug"
- # PROP BASE Use_Debug_Libraries 1
- # PROP BASE Output_Dir ""
- # PROP BASE Intermediate_Dir ""
- # PROP BASE Cmd_Line "NMAKE /f makefile.win"
- # PROP BASE Rebuild_Opt "/a"
- # PROP BASE Target_File "/Apache2.0/bin/Apache.exe"
- # PROP BASE Bsc_Name "./Browse/BuildBin.bsc"
- # PROP BASE Target_Dir ""
- # PROP Use_Debug_Libraries 1
- # PROP Output_Dir ""
- # PROP Intermediate_Dir ""
- # PROP Cmd_Line "NMAKE /f makefile.win INSTDIR="/Apache2" LONG=Debug _tryssl _tryzlib _dummy"
- # PROP Rebuild_Opt ""
- # PROP Target_File "/Apache2/bin/Apache.exe"
- # PROP Bsc_Name "./Browse/Apache.bsc"
- # PROP Target_Dir ""
- !ENDIF
- # Begin Target
- # Name "BuildBin - Win32 Release"
- # Name "BuildBin - Win32 Debug"
- !IF "$(CFG)" == "BuildBin - Win32 Release"
- !ELSEIF "$(CFG)" == "BuildBin - Win32 Debug"
- !ENDIF
- # Begin Source File
- SOURCE=./os/win32/BaseAddr.ref
- # End Source File
- # Begin Source File
- SOURCE=./CHANGES
- # End Source File
- # Begin Source File
- SOURCE=./Makefile.win
- # End Source File
- # Begin Source File
- SOURCE=./STATUS
- # End Source File
- # End Target
- # End Project
为了进行对比,给出工程yang的yang.dsp文件内容:
- # Microsoft Developer Studio Project File - Name="yang" - Package Owner=<4>
- # Microsoft Developer Studio Generated Build File, Format Version 6.00
- # ** DO NOT EDIT **
- # TARGTYPE "Win32 (x86) Console Application" 0x0103
- CFG=yang - Win32 Debug
- !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 "yang.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 "yang.mak" CFG="yang - Win32 Debug"
- !MESSAGE
- !MESSAGE Possible choices for configuration are:
- !MESSAGE
- !MESSAGE "yang - Win32 Release" (based on "Win32 (x86) Console Application")
- !MESSAGE "yang - Win32 Debug" (based on "Win32 (x86) Console Application")
- !MESSAGE
- # Begin Project
- # PROP AllowPerConfigDependencies 0
- # PROP Scc_ProjName ""
- # PROP Scc_LocalPath ""
- CPP=cl.exe
- RSC=rc.exe
- !IF "$(CFG)" == "yang - 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 ""
- # ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
- # ADD CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
- # ADD BASE RSC /l 0x804 /d "NDEBUG"
- # ADD RSC /l 0x804 /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 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:console /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 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:console /machine:I386
- !ELSEIF "$(CFG)" == "yang - 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 ""
- # ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /GZ /c
- # ADD CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /FR /YX /FD /GZ /c
- # ADD BASE RSC /l 0x804 /d "_DEBUG"
- # ADD RSC /l 0x804 /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 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:console /debug /machine:I386 /pdbtype:sept
- # 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 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:console /debug /machine:I386 /pdbtype:sept
- !ENDIF
- # Begin Target
- # Name "yang - Win32 Release"
- # Name "yang - Win32 Debug"
- # Begin Group "Source Files"
- # PROP Default_Filter "cpp;c;cxx;rc;def;r;odl;idl;hpj;bat"
- # Begin Source File
- SOURCE=./main.cpp
- # End Source File
- # End Group
- # Begin Group "Header Files"
- # PROP Default_Filter "h;hpp;hxx;hm;inl"
- # End Group
- # Begin Group "Resource Files"
- # PROP Default_Filter "ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe"
- # End Group
- # End Target
- # End Project
对比yang.dsp 和buildall.dsp两个文件,可以发现其共同之处在于他们都包含了CFG定义、Project section,Project中还包含了Target section,而Target中又包含了source section。其中CFG的值表示编译的版本是Debug还是release,该值可以通过VC的Build->configurations菜单来设置。yang.dsp在Project section中通过以下部分配置来编译源代码和资源文件:
- # ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
- # ADD CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
- # ADD BASE RSC /l 0x804 /d "NDEBUG"
- # ADD RSC /l 0x804 /d "NDEBUG"
其中CPP=cl.exe,RSC=rc.exe是VC的代码编译器和资源编译器,编译的文件由后续的Source section定义。 Project section还使用bscmake.exe来进行编译:
- BSC32=bscmake.exe
- # ADD BASE BSC32 /nologo
- # ADD BSC32 /nologo
我在网上搜到的bscmake.exe说明为:.BSC格式文件是浏览信息文件,由浏览信息维护工具(BSCMAKE)从原始浏览信息文件(.SBR)中生成,BSC文件可以用来在源代码编辑窗口中进行快速定 位。用于浏览项目信息的,如果用source brower的话就必须有这个文件。可以在project options里去掉Generate Browse Info File,这样可以加快编译进度。 在定义编译之后还使用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 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:console /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 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:console /machine:I386
从以上过程中可以看出,yang.dsp 文件的Project定义了整个workspace的编译过程,包括使用cl.ext 程序进行编译和link.exe进行链接。 而在apache的Buildall.dsp文件中,Project部分没有使用cl.exe 和link.exe来定义编译和链接方式,而是进行了如下定义:
- # PROP Cmd_Line "NMAKE /f makefile.win INSTDIR="/Apache2" LONG=Debug _tryssl _tryzlib _dummy"
该定义将使得VC使用name /f makefile.win 进行编译,而makefile.win 是apapche源码中包含的makefile文件,如此编译的所有操作都由makefile.win 文件进行控制。 Project中包含Target section,Target section中会定义所有要编译的源代码,它会包含很多Source section,yang.dsp把所有添加到项目中的源程序文件:main.cpp 和资源文件都添加进来,并且还分成了两个group,一个是source code group和 还有一个是Resource Files group,这两个分别是用cl.exe 和rc.exe进行编译。 而在buildall.dsp文件中,由于已经通过name /f makefile.win 进行编译,我猜测Source section部分的定义已经没有意义了。 在source section部分,还可以编写类似makefile中文件依赖关系在其中,apache中包含一个子project:apr,其对应的apr.dsp文件中部分的source section内容为:
- SOURCE=./include/apr.hnw
- # PROP Exclude_From_Build 1
- # End Source File
- # Begin Source File
- SOURCE=./include/apr.hw
- !IF "$(CFG)" == "apr - Win32 Release"
- # Begin Custom Build - Creating apr.h from apr.hw
- InputPath=./include/apr.hw
- "./include/apr.h" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)"
- type ./include/apr.hw > ./include/apr.h
- # End Custom Build
- !ELSEIF "$(CFG)" == "apr - Win32 Debug"
- # Begin Custom Build - Creating apr.h from apr.hw
- InputPath=./include/apr.hw
- "./include/apr.h" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)"
- type ./include/apr.hw > ./include/apr.h
- # End Custom Build
- !ENDIF
- # End Source File
- # Begin Source File
- SOURCE=./include/apr_allocator.h
- # End Source File
在以上定义中,"./include/apr.h" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)" 定义了apr.h文件依赖于apr.hw文件,如果apr.hw文件发生了变化,则执行type ./include/apr.hw > ./include/apr.h指令把apr.hw内容拷贝到apr.h文件(type是dos的命令,把文件内容进行输出),这也解释了为何在下载的源码里不包含apr.h文件,但编译后就包含了该文件。 三、Visual C++ workspace组织和Project编译控制小结 VC 通过.dsw 文件来管理和存储workspace中配置和project,它定义了每个Project和他们之间的依赖关系。而.dsp 文件定义了对应project的编译配置信息,VC通过该文件对代码进行编译,我们也可以通过修改该文件而采用nmake的makefile来进行编译。
|