On Wed, August 16, 2006 03:19, Bart Samwel wrote: > Rabin Nathan wrote: >> Is there a work around for this so that LD_LIBRARY_PATH does not have to >> be set each time? I am concerned that when I eventually send my program >> to some web hosting company they may not take kindly to LD_LIBRARY_PATH.
> Well, that is probably going to be problematic at some web hosting > companies. Perhaps you can compile libpq statically to a .a library? I > don't know if it supports this, but it would make things a lot easier > for you. I agree. LD_LIBRARY_PATH is useful for testing, but you'll probably want to avoid it otherwise. That means either installing the more recent version of libpq in the regular place, or linking statically (or just using the older libpq, of course, but I'll assume you don't want to do that). One way to link to libpq statically that I think should work is just to include the filename of libpq.a (including its full path!) in the command line that links your program, i.e. use libpq.a as if it were a regular object file. Jeroen _______________________________________________ Libpqxx-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/libpqxx-general
