Re: [Firebird-devel] Porting Firebird

[Tagangout, A. <Abd...@me...>]

Hi Alex,
Many thanks, and it will be vary beutiful if there is a Documentation for this issue.
Abdo 


MEP Kutsch GmbH & Co. KG
Flaßkuhle 1
58452 Witten
Tel. : 02302 28262-41
Fax.: 02302 28262-99

mailto:abd...@me...

http://www.mep.de

-----Ursprüngliche Nachricht-----
Von: Alex Peshkoff [mailto:pes...@ma...] 
Gesendet: Freitag, 1. Oktober 2010 09:41
An: fir...@li...
Betreff: Re: [Firebird-devel] Porting Firebird

 On 09/29/10 18:17, Enrico Weigelt wrote:
> Hi folks,
>
>
> IMHO it would be a better approach to fork into new branch and step by 
> step trim down until only the client library ist left.
> (that fork will be frequently rebased to upstream to keep up).
>
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. 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.
Seems trivial, specially if one agrees to skip steps 2 and 3 - i.e. for blob-less client one can simply start cross build of library.

I will commit this soon, and may be client from version 3 will be the most simple solution.


------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel