Re: Static Build

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: <APendleton(at)vgsinc(dot)com>
Cc: <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Static Build
Date: 2003-06-11 18:03:46
Message-ID: 50194.80.177.99.193.1055354626.squirrel@ssl.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

It's rumoured that Adam Pendleton once said:
> I keep hearing that a static version of pgAdmin3 is desired, so I
> thought that I would just squash the thought before it gets to far. It
> would be next to impossible to release a static version of pgAdmin3
> because of the large number of dependencies of the program. Keep in
> mind, that just because we link against a static version of the
> wxWindows library, doesn't mean that we aren't using shared symbols.
> We would also need static versions of glibc, PostgreSQL, and any
> libraries against which any of those programs link. We would need to
> be able to pull in static code for *every* library that our program
> touches, or any library that a library our program touches touches. I
> think statically linking against wxWindows is a good idea, since it is
> not likely to be available on client machines, but to statically link
> against something like the GNU C Library is just an unnecessary
> headache, since it's not unreasonable to require a client to have that
> library installed (every other program on the machine requires it
> too!). Just my 2 cents.

Hi Adam,

That sounds sensible. I think we're all pretty much settled on wx2.5 now
as well, so how about the following (for the Unix build - Win32 is a whole
other matter):
1) We make GTK2/wx25/Unicode requirements, and thus get rid of the
associated configure options. If we're producing mainly binary releases
anyway, this should only be a problem for those who want to compile on
older systems, from source.
Q. Is the GTK2 stuff can either be statically linked into wx or is it
common enough these days that we needn't worry about it?
2) We statically link wx and libpq. Currently libpq is dynamically linked.
This of course removes the requirement for PostgreSQL to be installed on
the target machine.
Q. To get SSL support we need to compile PostgreSQL with OpenSSL. Are
there any legal ramifications for this?
If we can do this, I think all we need is a --enable-debug option in
addition to --with-wx & --with-pgsql.
Thoughts, comments? Am I insane?

Regards, Dave

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Jean-Michel POURE 2003-06-11 18:10:39 Re: Static Build
Previous Message Jean-Michel POURE 2003-06-11 17:57:54 Re: wxWindows configuration under Suse 8.2