Dave Page wrote:
> I'd be happy to go with the embedded bundle option - what puts me off is
> that I'm still not overly confident with make etc. The merged code
> option is nicest in theory, but I'd be concerned that it would always
> seem like bolted on code without an almost complete rewrite (which seems
> pointless - Korry's code is perfectly good, just architected very
> differently from the rest of pgAdmin).
>
> If you can track down any info on embedded bundles, that would be a big
> help. I suspect this is the method that would be the most sensible overall.
For info, I'm just about to commit changes that do exactly this - build
a Debugger.app within the pgAdmin3.app resources directory - it seems to
work fine, with one caveat:
The existing complete-bundle.sh code works fine, and rewrites the paths
to the wx libraries as expected, however the debugger crashes when run.
As best I can figure, this is because although the debugger has the
correct relative paths to the libraries, some of those (wx) libraries
are interdependent, and when run by the debugger executable, the
relative paths between them are incorrect.
To resolve this until a better solution is found, I've modified the
build system such that static linking is forced when building an app
bundle. This also has the advantage of reducing the bundle size a little :-)
Regards, Dave.