8
0
mirror of https://github.com/FirebirdSQL/firebird.git synced 2025-01-22 18:03:03 +01:00

Update MSVC build instructions

This commit is contained in:
asfernandes 2006-05-27 18:07:27 +00:00
parent 672ab6b3fb
commit 4cf282a114

View File

@ -11,13 +11,13 @@
<BODY>
<H2>VisualStudio build Notes</H2>
<hr/>
Last Update: July 16 2003<br>
Last Update: May 27 2006<br>
Author: Blas Rodriguez Somoza <a href="">blas@puertareal.com</a><br>
<h3>0.-Introduction</h3>
<blockquote>
<p>There are two VisualStudio builds, msvc6 and msvc7. The msvc6 build is the official build of FB in win32.</p>
<p>There are two VisualStudio builds, msvc6 and msvc7. The msvc7 build is the official build of FB in win32.</p>
<p>Under the directory where you put Firebird2 sources you will see the following directories</p>
<ul>
<li>builds</li>
@ -58,20 +58,17 @@ Author: Blas Rodriguez Somoza <a href="">blas@puertareal.com</a><br>
<h3>2.-Prerrequisites</h3>
<blockquote>
<p>To prepare the standard msvc6 build of FB you need:</p>
<p>To prepare the standard msvc build of FB you need:</p>
<ul>
<li>Microsoft VisualStudio 6 or 7.</li>
<li>A running Firebird server</li>
<li>sed unix utility</li>
</ul>
<p>If you intend to modify the dsql parser file (parse.y) you will need a parser generator, bison or byacc (Berkeley yacc). At this time byacc 1.9 is the official parser generator although in the future it will be switched to bison. The tested versions of byacc are 1.9 or newer and for bison 1.28 or newer.</p>
<p>If you intend to prepare an installable build, you will need innosetup.</p>
<p>To download the utilities use the following links</p>
<ul>
<li>My Inno setup extensions 3.0.6.2 <a href="http://www.wintax.nl/isx/">http://www.wintax.nl/isx/</a></li>
<li>Sed and Bison 1.35 <a href="http://gnuwin32.sourceforge.net/">http://gnuwin32.sourceforge.net/</a></li>
<li>Byacc 1.9 <a href="ftp://garbo.uwasa.fi/pc/unix/">ftp://garbo.uwasa.fi/pc/unix/</a></li>
<li>Sed <a href="http://gnuwin32.sourceforge.net/">http://gnuwin32.sourceforge.net/</a></li>
</ul>
</blockquote>
@ -86,7 +83,7 @@ Author: Blas Rodriguez Somoza <a href="">blas@puertareal.com</a><br>
</li>
</ol>
<h4>2.2.-Sed and bison</h4>
<h4>2.2.-Sed</h4>
<h4>2.3.-Inno setup</h4>
@ -100,18 +97,17 @@ Author: Blas Rodriguez Somoza <a href="">blas@puertareal.com</a><br>
<li>Go to the firebird2\builds\win32 directory.</li>
<li>Run the following batches in order (your version of VisualStudio is detected automatically)</li>
<ol>
<li>prepare.bat [FIREBIRD]</li>
<li>make_boot.bat</li>
<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 firebird2 directory.</p>
<p>After the build finish, an output directory with the binaries is created below your firebird2 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>Remember, you need sed and bison or yacc in the path to rebuild the parser</p>
<p>If you change parser.cpp or parser.sed you will need to rebuild parser.cpp, to do so use parser.bat</p>
<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>
@ -129,8 +125,8 @@ Where DEBUG means if the build is a debug one or not and CS means classic server
</ul>
<h4>4.4.-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 firebird2\output\examples\build_win32 and run build_all.bat</p>
<p>Build_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>If you want to build the examples just cd to firebird2\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>