Re: [Firebird-devel] Compile Firebird Client for ARM9 CPU

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

 On 01/31/11 01:29, Enrico Weigelt wrote:
> * Alex Peshkoff <pes...@ma...> schrieb:
>>  On 01/17/11 20:04, Tagangout, Abderrahim wrote:
>>> Hi Axel,
>>> yes of course, i wanna solve this. But if it is possible can you give me an step per step on how to do this?
>>> I'm new on the world of Database.
>>> In the feature, i need to have a connection from an Embedded Module (Based on ARM9)to the Firebird-Server on a Server Machine.
>> 1. First of all you should download trunk from our svn:
>> svn co https://firebird.svn.sourceforge.net/svnroot/firebird/firebird/trunk
>> and complete x86 build. This is needed to preprocess all ESQL (*.epp)
>> files to cpp one.
> I still don't understand why these files still generated from an
> _running_ database instead instead of just taking a simple textfile 
> as the primary datasource for both generated .cpp files and the
> initial sql dumps ?
>
I've explained it many times, can't add something new...
>> 3. Now you must manually change src/include/gen/autoconfig.h to make it
>> match ARM9 hardware (pay special attention to sizes, alignment,
>> endianess). You will also have to:
> This defeats the whole purpose of autofool and is a maintenance hell.
>
This advice was not for maintenance, just to perform first build.
BTW, all our windows builds are done in that manner. There is
autoconfig_msvc.h, which is copied to autoconfig.h somewhere in
build_all.bat. Not ideal (far not), but it works.
>> 4. After it you may change your build environment to cross-compiler
>> (make sure that g++/gcc matches cross-compiler) and run:
>> make TARGET=Release fbclient
>> (or TARGET=Debug if you want, in that case at step 1 you should run
>> 'make Debug')
> I guess, passing the right toolchain commands to make (via CC=...
> LD=..., etc) is enough, right ?
>
I think yes.
>> Certainly, I may miss something.
> Yes, you'll have to look through the generated makefiles that CFLAGS
> and LDFLAGs are also set up properly (eg. NOT pointing to the host
> system, only to the target toolchain), otherwise you're likely to get
> nasty side effect you'll just notice when it's too late.
We have separate file to set them, make.platform.
And I've recommended to use one for ARM.