Re: [Firebird-devel] Porting Firebird

[Alex P. <pes...@ma...>]

 On 10/01/10 21:41, Enrico Weigelt wrote:
> * Alex Peshkoff <pes...@ma...> schrieb:
>
> Hi,
>
>> Almost it is done (but not committed yet) in trunk. yValve is present
>> (but actually this is no danger), but the overall process of library
>> build became absolutely clear. 
> where can I get this tree ?
>
It will be committed in trunk soon (you know we changed from CVS to SVN).
If you want it as fast as possible, just let me know - I can send it to
you privately.
>> And (what should be most interesting from
>> this thread POV) library is built as the first step, right after
>> building gpre_boot.
>>> *After* then, care about crosscompiling. 
>> It can looks as follows:
>> 1. Build host gpre_boot (can be avoided if one needs no blobs and arrays).
>> 2. Preprocess 2 epp files.
>> 3. Cross-build firebird library.
> What exactly is gpre_boot required for ?
Some high-level ISC API calls (blobs and arrays support) are implemented
using gdml.
> Is it still so, that preprocessing the .epp files requires an running
> database instance ?
>
For engine build process we do not need to preprocess .epp files with
anything else except gpre_boot, which does not require database
instance. But to build some plugins (like security database management)
and some utilities (qli) full gpre and therefore running instance are
required. Must say that both can be rewritten to use SQL.