On Sun, 25 Jan 2009, Andrew Hall wrote:
> We have been using Mac OS X 10.5 XCode 311, Firebird 211 Classic 32 bit with
> FPC 224 (which contains the fix for the framework .dylib extension so that
> libfbclient.dylib can be located). This works with FPC, FlameRobin and
> RazorSQL. However, reading Firebird's recommendation that unless there is a
> good reason, SuperServer should be used we have attempted this conversion.
> Switching to SuperServer 32 bit, FlameRobin and RazorSQL continue to work -
> but FPC raises an exception. EInOutError : Can not load default Firebird
> clients ("libgds.dylib" or "libfbclient.dylib"). Check your installation.
> When the Framework is opened in the OS X library we confirm that
> libfbclient.dylib is no longer found (although the other 4 library files
> remain).
>
> Questions
> 1) Can FPC work with Firebird SuperServer - if so, what configuration changes
> are required or does the FPC library required modification?
It can, and no change should be necessary.
> 2) Is there other advice the forum can offer (eg. does Classic remain a
> reasonable choice, is SuperServer support planned, etc).
>From the client perspective, there is no difference whatsoever whether
you are running superserver or classic. I use both.
The problem you are experiencing is an installation problem, not an
architectural problem. For some reason, the FPC application fails to
find the libraries. However, I have no idea why this happens.
I'm not a Mac OS X expert, so I can't help with that.
As far as the 'recommendation' is concerned: for systems with multiple
CPUs it is better to use Classic server, as Superserver can use only
1 processor. The upcoming version 2.5 of Firebird should remedy that.
Michael.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
