> While this is a reasonable solution for people who do their compiling on
> the command line, it is not a reasonable solution for people who are using
> ide's, or who compile with ant or maven.

Agree.

> I would be happy to work with you on different search strategies for these
> libraries. Both dll's should be somewhere easily configured by either
> being placed in the same directory as the database or reachable from a
> properties file (the better solution for jaybird.dll.
>
> You can't consider this embedded code unless all pieces of it are
> embedded.

Well.. the issue is complicated. For now we can create a solution that loads
libraries from the specified paths, that will work with FB 1.5 and FB 2.0
unless application does not need firebird.conf. When application needs
firebird.conf (for example when it needs fbintl.dll or UDFs), only a custom
build helps us.

Things get worse when we consider Vulcan - it cannot run without its
configuration and there are no means to specify configuration during
attachment. I had a long discussion about this issue with Jim Starkey, who
is Vulcan architect, but we could not find a common ground. So, the only
solution for Vulcan is a custom build.

Therefore I have stopped any development in that direction, since it is not
yet clear where it goes.

If you need partial solution for FB 1.5 and FB 2.0, then that is easier -
appropriate code for library loading is already in CVS (it even can extract
jaybird.dll and fbembed.dll from a jar in classpath), the only missing thing
is a parameter with the path.

Roman