From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Miha Radej" <miha(dot)radej(at)siix(dot)com>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: problem compiling, error while checking for wx |
Date: | 2005-10-20 07:15:49 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC35B5@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org
> [mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of Miha Radej
> Sent: 20 October 2005 00:46
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] problem compiling, error while
> checking for wx
>
> i've successfully used the above pgadmin configure command
> until a few
> days ago. configure goes through and pgadmin compiles ok with the
> following parameters:
> ./configure --prefix=/usr/local/pgadmin-svn --enable-debug
> --enable-static
>
> is it necessary to explicitly add these two parameters now?
Yes - previously it was pretty undertermined - in fact you pretty much
always got a debug build (this was more apparent on Mac where the
resulting executable was around 128MB!).
It will default now to dynamic linking, non-debug, and if you don't have
an appropriately configured wx installation to match you'll get the
errors you see. So, you can either:
- Pass the configure options to pgAdmin to tell it to build correctly
with your wx installation
- Rebuild wx with the right configuration to match pgAdmin. This is
perhaps the better option because you can build all 4 possible
combinations and install them over the top of each other. Don't forget
the 'make clean' before each build though, otherwise bad things will
happen.
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2005-10-20 07:19:54 | SVN Commit by dpage: r4574 - trunk/www/pgadmin3/cnt |
Previous Message | Miha Radej | 2005-10-20 02:44:54 | does this string need correction? |