Florian G. Pflug wrote:
> Think I found the foobarization...
> So I least at that point I was aware that we are walking on thin ice with
> how we integrate pg_dump and friends into the bundle. Seems that using a
> version of libpq that doesn't link to the system provided libssl, but to
> a custom version instead (and thereby breaking that "doesn't have
> that live inside the pgadmin bundle" assumtion)is enough to let the ice
Or any library not directly linked to the executable itself.
> The only really correct fix would be to use @loader_path instead of
> @executable_path when referencing shared libraries (@loader_path is the
> path of the image *requireing* the lib, instead of the top-level
> executable) -
> but that means dropping support for 10.3 :-(.
Yeah, I'm not sure we should do that just yet.
> One alternative that I can
> see is
> to put pg_dump and friends into Contents/SharedSupport directly - that way,
> the relative path from pg_dump to Contents/Frameworks is that same as for
> main pgAdmin executeable (which lives in Contents/MacOS). Not exactly
> but hey, who looks into the bundle anyway?
Jyrki; the attached patch should implement what Florian is suggesting -
can you test it please? Make sure you run the bootstrap script, and to
be on the safe side, remove your preferences file as well.
In response to
pgadmin-hackers by date
|Next:||From: svn||Date: 2007-08-06 10:52:54|
|Subject: SVN Commit by dpage: r6538 - trunk/pgadmin3/docs/en_US|
|Previous:||From: Dave Page||Date: 2007-08-05 13:38:27|
|Subject: Re: Syntax highlight colors in ctlSQLBox|