Hi,
Le 09/12/11 01:52, Lionel Elie Mamane a écrit :
Now that I think of it, since libpq is in a path like
/Library/PostgreSQL/9.1/lib/libpq.5.dylib, how is it supposed to be
found by the dynamic linker at runtime? That's probably the problem,
unless that directory is added to the equivalent of /etc/ld.so.conf on
GNU/Linux... Try: otool -L
/path/to/your/postgresql-sdbc-impl.uno.dylib If that's indeed the
problem, you can solve it with the DYLD_LIBRARY_PATH envvar, but then,
how do we fix it for *all* our users (that have an ABI-compatible
libpq installed) automatically, since their libq.5.dylib may be at
another path than on our build machine? Or maybe MacOS X work "à la
Microsoft Windows" for libraries in that every application is supposed
to bundle a copy of every dynamic library it uses? I wouldn't have
expected so.
If I compare with the postgres OXT file on Linux, the connector includes
the impl.uno file, which weighs in at 6.2Mb uncompressed. However, the
Mac OXT in comparison does not include the impl.uno file in its bundle,
so maybe it is just a packaging issue ?
Alex
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.