Re: portable pgsql binary/pkg building on OSX ...

On Oct 5, 2005, at 6:34 PM, OpenMacNews wrote:

>
> (1) to build STATIC pgsql* binaries, with NO external lib
> dependencies, is
> '--disable-rpath' necessary/sufficient?

I don't think so, but I'm hardly and expert here. I was able to build
psql with libq as a single executable, but in the end I found it
easier to do the standard compile and then have a script run
install_name_tool to make psql look for libq in a relative directory.

>
> (2) i've not (yet) tried static bins on different OSX ver deployment
> targets
> (10.4.x, 10.3.x, etc.) and/or different CPUs (G3/G4/G5).
>
> how portable *are* built pgsql bins? cross-compile across
> platforms/cpu-families/OS's is clear, but do i need to worry abt it
> for OSX
> ver/cpu variants?

I don't think you have to worry about CPUs, but OS version might be a
problem. I think this is why I decided to make the second version of
pgEdit OS X 10.3 plus. If it helps you, here is what my external
dependencies for psql look like which seems to work OK on 10.3 and 10.4

otool -L psql
psql:
@executable_path/libpq.4.0.dylib (compatibility version
4.0.0, current version 4.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/lib/libresolv.9.dylib (compatibility version 1.0.0,
current version 324.9.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 71.1.1)

When you say no external dependencies, are you really going to
include the system libraries in your package?

John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL