At 12:18 PM 19/04/2004 +0800, you wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On Friday 16 April 2004 22:03, George P Boutwell wrote:
> > > -----Original Message-----
> > > Any pointers anyone?? i'm using FB1.5 final release...
> > > thanks..
> >
> > Hmm... I'm not using FBEmbed under Linux yet, but under windows I had to
> > copy the dynamic link libraries fbemebed.dll & ib_util.dll, the
> > firebird.msg file, & the firebird.conf files. Have you read the release
> > notes? They are pretty clear on what needs to be in the application
> > directory and what doesn't.
>
>I tried using the info for the Windows Embed installation.. It doesn't
>seem to
>work for Linux... When i try running ISQL, it will just crash out.. without
>any error message at all.. I've got the following files in the app directory
>
>libfbembed.so.1
>libib_util.so
>firebird.msg
>firebird.conf
>aliases.conf
>isql
>intl/fbintl
>isc_event1.xxxx
>isc_init1.xxxx
>isc_lock1.xxxx
>
>Any help??

Yes -- stop trying. There isn't an equivalent to fbembed.dll for Linux
(one that uses the ordinary API client and a Superserver instance).

Ordinary Classic on Linux with libfbembed.so client is the nearest to
"equivalent" there is. You can do "embedded applications" with this
combination, i.e. using a special flavour of SQL (called "embedded SQL' ,
or ESQL) and using a direct local connect. Architecturally, it is quite
different.

If you want the near-equivalent of Windows embedded on Linux, just write an
ordinary API client and connect it to the Classic server, using
libfbembed.so or libfbclient.so as your library. libfbclient.so is a less
bloated library and is more thread-friendly than the old libfbembed.so.

The Classic "server" on Linux isn't "serving" anything until you connect to
it. It's just a gleam in the eye of xinet, which lives on the OS (isn't
part of Firebird).

btw, for remote Linux clients, use only libfbclient.so.

/heLen