最近下载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文件,发现其内容如下:
[cpp] view plaincopy
1. Project: "Apache"="./Apache.dsp" - Package Owner=<4>
2. Package=<5>
3. {{{
4. }}}
5. Package=<4>
6. {{{
7. Begin Project Dependency
8. Project_Dep_Name libapr
9. End Project Dependency
10. Begin Project Dependency
11. Project_Dep_Name libaprutil
12. End Project Dependency
13. Begin Project Dependency
14. Project_Dep_Name libhttpd
15. End Project Dependency
16. }}}
17. ###############################################################################
18. #此处省略许多Project,只以libapr为例说明
19. #.....
20. ###############################################################################
21. Project: "libapr"="./srclib/apr/libapr.dsp" - Package Owner=<4>
22. Package=<5>
23. {{{
24. }}}
25. Package=<4>
26. {{{
27. }}}
28. #
29. #后续省略许多Project,只以libapr为例说明
30. #.....
为了分析和研究dsw文件的格式,我用VC6建立新建一个名字为yang的项目,并添加一个main.cpp文件到该工程中,之后VC6自动生成了Project的项目文件 :yang.dsw和yang.dsp文件,打开yang.dsw文件,其内容如下:
[cpp] view plaincopy
1. Project: "yang"=./yang.dsp - Package Owner=<4>
2. Package=<5>
3. {{{
4. }}}
5. Package=<4>
6. {{{
7. }}}
8. Global:
9. Package=<5>
10. {{{
11. }}}
12. Package=<3>
13. {{{
14. }}}
15. ###############################################################################
对比yang.dsw和apache.dsw格式,便可以发现dsw文件中包含两类Entry:Project和Global。一个dsw文件中可以包含多个Porect Entry(我不知Entry表述是否准确,但我没搜索到dsw文件格式说明,故采用Entry一说),如果包含了多个Project Entry说明该Workspace中含有多个Projects。每一个Project Entry开头为:
[cpp] view plaincopy
1. Project:"yang"=./yang.dsp - Package Owner=<4>
其中yang是指project名字,每一个Project包含两个Package:Package=<5>和Package=<4>,如果同一个workspace中的多个Project之间有依赖关系,则会在Package=<4>中进行描述,如Apache.dsw中的Apacheproject的其中一个依赖关系定义为:
[cpp] view plaincopy
1. Begin Project Dependency
2. Project_Dep_Name libapr
3. 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之后添
[cpp] view plaincopy
1. ###############################################################################
2. Project: "zhang"=./zhang.dsp - Package Owner=<4>
3. Package=<5>
4. {{{
5. }}}
6. Package=<4>
7. {{{
8. }}}
保存后使用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全称是DeveloperStudio Project,是一个配置文件,它记录的是一个项目的所有配置信息,纯文本文件,主要用于配置编译。打开BuildBin.dsp文件,可以看到:
[cpp] view plaincopy
1. # Microsoft Developer Studio Project File - Name="BuildBin" - Package Owner=<4>
2. # Microsoft Developer Studio Generated Build File, Format Version 6.00
3. # ** DO NOT EDIT **
4. # TARGTYPE "Win32 (x86) External Target" 0x0106
5. CFG=BuildBin - Win32 Debug
6. !MESSAGE This is not a valid makefile. To build this project using NMAKE,
7. !MESSAGE use the Export Makefile command and run
8. !MESSAGE
9. !MESSAGE NMAKE /f "BuildBin.mak".
10. !MESSAGE
11. !MESSAGE You can specify a configuration when running NMAKE
12. !MESSAGE by defining the macro CFG on the command line. For example:
13. !MESSAGE
14. !MESSAGE NMAKE /f "BuildBin.mak" CFG="BuildBin - Win32 Debug"
15. !MESSAGE
16. !MESSAGE Possible choices for configuration are:
17. !MESSAGE
18. !MESSAGE "BuildBin - Win32 Release" (based on "Win32 (x86) External Target")
19. !MESSAGE "BuildBin - Win32 Debug" (based on "Win32 (x86) External Target")
20. !MESSAGE
21. # Begin Project
22. # PROP AllowPerConfigDependencies 0
23. # PROP Scc_ProjName ""
24. # PROP Scc_LocalPath ""
25. !IF "$(CFG)" == "BuildBin - Win32 Release"
26. # PROP BASE Use_Debug_Libraries 0
27. # PROP BASE Output_Dir ""
28. # PROP BASE Intermediate_Dir ""
29. # PROP BASE Cmd_Line "NMAKE /f makefile.win"
30. # PROP BASE Rebuild_Opt "/a"
31. # PROP BASE Target_File "/Apache2.0/bin/Apache.exe"
32. # PROP BASE Bsc_Name "./Browse/BuildBin.bsc"
33. # PROP BASE Target_Dir ""
34. # PROP Use_Debug_Libraries 0
35. # PROP Output_Dir ""
36. # PROP Intermediate_Dir ""
37. # PROP Cmd_Line "NMAKE /f makefile.win INSTDIR="/Apache2" LONG=Release _tryssl _tryzlib _dummy"
38. # PROP Rebuild_Opt ""
39. # PROP Target_File "/Apache2/bin/Apache.exe"
40. # PROP Bsc_Name "./Browse/Apache.bsc"
41. # PROP Target_Dir ""
42. !ELSEIF "$(CFG)" == "BuildBin - Win32 Debug"
43. # PROP BASE Use_Debug_Libraries 1
44. # PROP BASE Output_Dir ""
45. # PROP BASE Intermediate_Dir ""
46. # PROP BASE Cmd_Line "NMAKE /f makefile.win"
47. # PROP BASE Rebuild_Opt "/a"
48. # PROP BASE Target_File "/Apache2.0/bin/Apache.exe"
49. # PROP BASE Bsc_Name "./Browse/BuildBin.bsc"
50. # PROP BASE Target_Dir ""
51. # PROP Use_Debug_Libraries 1
52. # PROP Output_Dir ""
53. # PROP Intermediate_Dir ""
54. # PROP Cmd_Line "NMAKE /f makefile.win INSTDIR="/Apache2" LONG=Debug _tryssl _tryzlib _dummy"
55. # PROP Rebuild_Opt ""
56. # PROP Target_File "/Apache2/bin/Apache.exe"
57. # PROP Bsc_Name "./Browse/Apache.bsc"
58. # PROP Target_Dir ""
59. !ENDIF
60. # Begin Target
61. # Name "BuildBin - Win32 Release"
62. # Name "BuildBin - Win32 Debug"
63. !IF "$(CFG)" == "BuildBin - Win32 Release"
64. !ELSEIF "$(CFG)" == "BuildBin - Win32 Debug"
65. !ENDIF
66. # Begin Source File
67. SOURCE=./os/win32/BaseAddr.ref
68. # End Source File
69. # Begin Source File
70. SOURCE=./CHANGES
71. # End Source File
72. # Begin Source File
73. SOURCE=./Makefile.win
74. # End Source File
75. # Begin Source File
76. SOURCE=./STATUS
77. # End Source File
78. # End Target
79. # End Project
为了进行对比,给出工程yang的yang.dsp文件内容:
[cpp] view plaincopy
1. # Microsoft Developer Studio Project File - Name="yang" - Package Owner=<4>
2. # Microsoft Developer Studio Generated Build File, Format Version 6.00
3. # ** DO NOT EDIT **
4. # TARGTYPE "Win32 (x86) Console Application" 0x0103
5. CFG=yang - Win32 Debug
6. !MESSAGE This is not a valid makefile. To build this project using NMAKE,
7. !MESSAGE use the Export Makefile command and run
8. !MESSAGE
9. !MESSAGE NMAKE /f "yang.mak".
10. !MESSAGE
11. !MESSAGE You can specify a configuration when running NMAKE
12. !MESSAGE by defining the macro CFG on the command line. For example:
13. !MESSAGE
14. !MESSAGE NMAKE /f "yang.mak" CFG="yang - Win32 Debug"
15. !MESSAGE
16. !MESSAGE Possible choices for configuration are:
17. !MESSAGE
18. !MESSAGE "yang - Win32 Release" (based on "Win32 (x86) Console Application")
19. !MESSAGE "yang - Win32 Debug" (based on "Win32 (x86) Console Application")
20. !MESSAGE
21. # Begin Project
22. # PROP AllowPerConfigDependencies 0
23. # PROP Scc_ProjName ""
24. # PROP Scc_LocalPath ""
25. CPP=cl.exe
26. RSC=rc.exe
27. !IF "$(CFG)" == "yang - Win32 Release"
28. # PROP BASE Use_MFC 0
29. # PROP BASE Use_Debug_Libraries 0
30. # PROP BASE Output_Dir "Release"
31. # PROP BASE Intermediate_Dir "Release"
32. # PROP BASE Target_Dir ""
33. # PROP Use_MFC 0
34. # PROP Use_Debug_Libraries 0
35. # PROP Output_Dir "Release"
36. # PROP Intermediate_Dir "Release"
37. # PROP Target_Dir ""
38. # ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
39. # ADD CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
40. # ADD BASE RSC /l 0x804 /d "NDEBUG"
41. # ADD RSC /l 0x804 /d "NDEBUG"
42. BSC32=bscmake.exe
43. # ADD BASE BSC32 /nologo
44. # ADD BSC32 /nologo
45. LINK32=link.exe
46. # 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
47. # 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
48. !ELSEIF "$(CFG)" == "yang - Win32 Debug"
49. # PROP BASE Use_MFC 0
50. # PROP BASE Use_Debug_Libraries 1
51. # PROP BASE Output_Dir "Debug"
52. # PROP BASE Intermediate_Dir "Debug"
53. # PROP BASE Target_Dir ""
54. # PROP Use_MFC 0
55. # PROP Use_Debug_Libraries 1
56. # PROP Output_Dir "Debug"
57. # PROP Intermediate_Dir "Debug"
58. # PROP Target_Dir ""
59. # ADD BASE CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /GZ /c
60. # ADD CPP /nologo /W3 /Gm /GX /ZI /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_MBCS" /FR /YX /FD /GZ /c
61. # ADD BASE RSC /l 0x804 /d "_DEBUG"
62. # ADD RSC /l 0x804 /d "_DEBUG"
63. BSC32=bscmake.exe
64. # ADD BASE BSC32 /nologo
65. # ADD BSC32 /nologo
66. LINK32=link.exe
67. # 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
68. # 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
69. !ENDIF
70. # Begin Target
71. # Name "yang - Win32 Release"
72. # Name "yang - Win32 Debug"
73. # Begin Group "Source Files"
74. # PROP Default_Filter "cpp;c;cxx;rc;def;r;odl;idl;hpj;bat"
75. # Begin Source File
76. SOURCE=./main.cpp
77. # End Source File
78. # End Group
79. # Begin Group "Header Files"
80. # PROP Default_Filter "h;hpp;hxx;hm;inl"
81. # End Group
82. # Begin Group "Resource Files"
83. # PROP Default_Filter "ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe"
84. # End Group
85. # End Target
86. # End Project
对比yang.dsp 和buildall.dsp两个文件,可以发现其共同之处在于他们都包含了CFG定义、Projectsection,Project中还包含了Target section,而Target中又包含了source section。其中CFG的值表示编译的版本是Debug还是release,该值可以通过VC的Build->configurations菜单来设置。yang.dsp在Project section中通过以下部分配置来编译源代码和资源文件:
[cpp] view plaincopy
1. # ADD BASE CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
2. # ADD CPP /nologo /W3 /GX /O2 /D "WIN32" /D "NDEBUG" /D "_CONSOLE" /D "_MBCS" /YX /FD /c
3. # ADD BASE RSC /l 0x804 /d "NDEBUG"
4. # ADD RSC /l 0x804 /d "NDEBUG"
其中CPP=cl.exe,RSC=rc.exe是VC的代码编译器和资源编译器,编译的文件由后续的Source section定义。
Project section还使用bscmake.exe来进行编译:
[cpp] view plaincopy
1. BSC32=bscmake.exe
2. # ADD BASE BSC32 /nologo
3. # ADD BSC32 /nologo
我在网上搜到的bscmake.exe说明为:.BSC格式文件是浏览信息文件,由浏览信息维护工具(BSCMAKE)从原始浏览信息文件(.SBR)中生成,BSC文件可以用来在源代码编辑窗口中进行快速定 位。用于浏览项目信息的,如果用source brower的话就必须有这个文件。可以在project options里去掉Generate Browse Info File,这样可以加快编译进度。
在定义编译之后还使用link.exe定义链接:
[cpp] view plaincopy
1. # 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
2. # 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来定义编译和链接方式,而是进行了如下定义:
[cpp] view plaincopy
1. # 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中包含Targetsection,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内容为:
[cpp] view plaincopy
1. SOURCE=./include/apr.hnw
2. # PROP Exclude_From_Build 1
3. # End Source File
4. # Begin Source File
5. SOURCE=./include/apr.hw
6. !IF "$(CFG)" == "apr - Win32 Release"
7. # Begin Custom Build - Creating apr.h from apr.hw
8. InputPath=./include/apr.hw
9. "./include/apr.h" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)"
10. type ./include/apr.hw > ./include/apr.h
11. # End Custom Build
12. !ELSEIF "$(CFG)" == "apr - Win32 Debug"
13. # Begin Custom Build - Creating apr.h from apr.hw
14. InputPath=./include/apr.hw
15. "./include/apr.h" : $(SOURCE) "$(INTDIR)" "$(OUTDIR)"
16. type ./include/apr.hw > ./include/apr.h
17. # End Custom Build
18. !ENDIF
19. # End Source File
20. # Begin Source File
21. SOURCE=./include/apr_allocator.h
22. # 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来进行编译。