> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > 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.
>
> AFAIK ODBC hasn't been compilable standalone for awhile; doesn't it
> depend on our toplevel configure script now?
The Unix version is not compilable on its own, but I see no code in
win32.mak that refers to upper directories.
>
> > Is it crazy to
> > put md5.c in interfaces/odbc and symlink it from there to backend/libpq
> > and interfaces/libpq?
>
> YES, that's crazy. If you think ODBC should build separately, then give
> it its own copy of md5.c. But please first check that your assumption
> is still valid.
And I will just throw a note at the top of each mentioning they should
be identical.
--
Bruce Momjian | http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
