> In trying to decide how to keep ODBC compilable standalone, I can't
> figure out how to get md5.c in there from backend/libpq. Is it crazy to
> put md5.c in interfaces/odbc and symlink it from there to backend/libpq
> and interfaces/libpq? I don't want to have two copies of md5.c but that
> may be another option. Opinions?
>
Seems to me that a stand-alone driver would have to have its own md5.c....
otherwise you may as well start linking in all kinds of code from the
distro. Of course that is what just about all other ODBC drivers do anyway.
Peter
