/
README.build.msvc.html
146 lines (136 loc) · 5.88 KB
/
README.build.msvc.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Build procedure for MSVC compiler</title>
</head>
<body>
<h2>VisualStudio build Notes</h2>
<hr/>
Last Update: March 23 2016<br>
Author: Blas Rodriguez Somoza <a href="">blas@puertareal.com</a><br>
Updated by: Popa Adrian Marius (mapopa at gmail.com)
<h3>0.-Introduction</h3>
<blockquote>
<p>There are a few VisualStudio solutions in the win32 folder . The msvc12 build is used for the official build of Firebird in Windows.</p>
<p>Under the directory where you put Firebird sources you will see the following directories</p>
<ul>
<li>builds</li>
<ul>
<li>mac_os_x (Mac os X build scripts)</li>
<li>posix (Posix build scripts)</li>
<li>win32 (Msvc build scripts)</li>
<li>.....</li>
</ul>
<li>doc</li>
<ul>
<li>sql.extensions</li>
</ul>
<li>src</li>
<ul>
<li>....</li>
</ul>
<ul>
<li>....</li>
</ul>
<li>examples</li>
<ul>
<li>....</li>
</ul>
</ul>
<p>After you build Firebird you also will see the following temporary directories</p>
<ul>
<li>gen (cpp files generated from epp, exe and fdb's.)</li>
<li>temp (compiler temporary)</li>
<li>output_Win32 (build output)</li>
</ul>
</blockquote>
<h3>1.-TODO</h3>
<blockquote>
</blockquote>
<h3>2.-Prerrequisites</h3>
<blockquote>
<p>To prepare the standard msvc build of FB you need:</p>
<ul>
<li>Microsoft VisualStudio 8 (2005) or greater</li>
<li>sed unix utility</li>
</ul>
<p>If you intend to prepare an installable build, you will need <a href=http://www.jrsoftware.org/isdl.php>innosetup 5</a></p>
<p>To download the utilities use the following links</p>
<ul>
<li>Innosetup (Note: This is the classic version, not the new unicode version.) <a href=http://www.jrsoftware.org/download.php/is.exe>http://www.jrsoftware.org/download.php/is.exe</a></li>
<li>Innosetup pack <a href="http://files.jrsoftware.org/ispack/ispack-5.3.10.exe">http://files.jrsoftware.org/ispack/ispack-5.3.10.exe</a></li>
<li>Sed <a href="http://gnuwin32.sourceforge.net/packages/sed.htm">http://gnuwin32.sourceforge.net/packages/sed.htm</a></li>
</ul>
</blockquote>
<h3>2.-Installing the utilities</h3>
<blockquote>
<h4>2.1.-Visual Studio</h4>
<ol>
<li>Install VisualStudio 20xx</li>
<li>You can compile it with <a href=http://www.visualstudio.com/downloads/download-visual-studio-vs#DownloadFamilies_4>Visual C++ 20xx Studio Express</a> but it will not be able to build the <a href=http://firebird.1100200.n4.nabble.com/building-head-with-visual-studio-2008-vc9-td1127168.html>control panel applet</a> but for the Firebird server and the rest of utilities building is ok<br>
</li>
</ol>
<h4>2.2.-Sed</h4>
<ol>
<li class="level1"><div class="li"> Download <a href="http://sourceforge.net/projects/gnuwin32/files/sed/4.2-1/sed-4.2-1-setup.exe/download" class="urlextern" title="http://sourceforge.net/projects/gnuwin32/files/sed/4.2-1/sed-4.2-1-setup.exe/download" rel="nofollow">Sed setup</a> from <a href="http://gnuwin32.sourceforge.net/packages/sed.htm" class="urlextern" title="http://gnuwin32.sourceforge.net/packages/sed.htm" rel="nofollow">GnuWin32 project</a> I had to run the setup and i extract into c:\gnuwin32 </div>
</li>
<li class="level1"><div class="li"> Add sed c:\gnuwin32\bin to the PATH environment variable , test it from a new console if it works by typing sed it should show you something abut gnu sed help</div>
</li>
</ol>
<h4>2.3.-Inno setup</h4>
<ol>
<li>Run the Installer for Innosetup 5 that you downloaded from above
setup-5.3.xx.exe</li>
<li>Run the Innosetup pack Installer ispack-5.3.10.exe
with the default options (next, next, next)</li>
<ol>
</blockquote>
<h3>4.- Building</h3>
<blockquote>
<h4>4.1.-Standard build</h4>
<ol>
<li>Eliminate the fb2control from Firebird solution if you are using Visual Studio Express (doesn't support MFC) and it's only the control panel applet and try to build it, it should give you no errors when you build the solution.</li>
<li>Open a command line window.</li>
<li>Go to the builds\win32 directory.</li>
<li>Run the following batches in order (your version of VisualStudio is detected automatically)</li>
<ol>
<li>make_icu.bat [DEBUG] [CLEAN]</li>
<li>make_boot.bat [DEBUG] [CLEAN]</li>
<li>make_all.bat [DEBUG] [CLEAN]</li>
</ol>
</ol>
<ul>
<p>After the build finish, an output directory with the binaries is created below your firebird directory.</p>
<li>To make a clean build from scratch after making changes to the code use the clean_all.bat script</li>
</ul>
<h4>4.2.-Parser rebuild</h4>
<p>If you change parser.y you will need to rebuild parser.cpp, to do so use parse.bat</p>
<h4>4.3.-Examples build</h4>
<p>The examples build prepare two databases that will be needed to compile the examples in a distribution. If you intend to prepare a distribution then run the examples batch before:</p>
<ol>
<li>make_examples.bat</li>
</ol>
<h4>4.4.-Installer build</h4>
<p>Remember, you need sed and innosetup in the path to build the installer</p>
<ul>
<li>Open a command line window.</li>
<li>Go to the builds\install\arch-specific\win32 directory.</li>
<li>The batch to build the installer is<br>
BuildExecutableInstall.bat [DEBUG] [CS]<br>
Where DEBUG means if the build is a debug one or not and CS means classic server installer.</li>
<li>After you start the batch, you will get a InnoSetup window. To build the install exe select the option compile, and a new exe will appear in builds/win32/install_image
</ul>
<h4>4.5.-Building samples</h4>
<p>After the standard build is finished, an output directory with the same structure as the installed FB directory is created.</p>
<p>If you want to build the examples just cd to firebird\output\examples\build_win32 and run run_all.bat</p>
<p>Run_all.bat calls four other bats to make the example sets. Any example set can be build independently with its make_XXX script.</p>
<p>The example sets are:</p>
<ul>
<li>api (API Interface)</li>
<li>dyn (embedded dynamic SQL)</li>
<li>stat (embedded static SQL)</li>
<li>udf (User defined functions)</li>
</ul>
</blockquote>
</body>
</html>