> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr]
> Sent: 18 June 2003 21:00
> To: pgadmin-hackers@postgresql.org
> Cc: Adam H. Pendleton; Jochem van Dieten; Dave Page
> Subject: Re: [pgadmin-hackers] pgAdmin3 feedback
>
>
> On Wednesday 18 June 2003 15:05, Dave Page wrote:
> > Yes, you need the symlink. It's there to provide a
> consistent name for
> > the config script no matter what build options wx was
> compiled with.
> > If you want to run with a non-standard wx installation, or the
> > non-default build, perhaps you can persuade Adam to add
> > --with-wx-config= option to override the script name?
>
> Yes, but the name of the wxGTK library can be guessed from
> these options: --enable-unicode => u --enable-debug => d
>
> /usr/bin/wxgtk2{u}{d}-2.5-config
>
> Users can be several wxGTK versions at once. One symlink
> cannot point to all
> version of wxGTK installed. For example, a user may need to install:
>
> - wxGTK 2.4 in shared mode,
> - wxGTK 2.5 cvs in shared mode with Unicode.
>
> A Symlink cannot be part of a wxGTK2.5 or a pgAdmin3 package.
> Or it would
> break existing wxGTK2.4 packages.
In which case an optional configure flag allows the user to select the
required config script. Whilst you can guess unicode and debug filenames
from the pgAdmin configure options, you cannot figure out what version
of wx is required (2.4 or 2.5), or if the user wants non-unicode linked
against GTK2.
For most people, the current behaviour fits with a standard wx
installation. For others, we can provide an override mechanism.
Regards, Dave.