Hi,

Just wanted to let you know that I was now finally able to build pgAdmin 1.16.1 
sources with wxWidgets 2.9.4 binaries using VS 2010 Professional. The issue 
with unresolved PQ symbols seemed to have been caused by a mismatch between 
32bit and 64bit versions; I was wanting to build a 32bit pgAdmin target but had 
used the EnterpriseDB installer only for a 64bit PostgreSQL.

Dave, to be able to build with the pre-built wxWidgets binaries, I had to tweak 
the linker configuration according to these instructions:
http://wxwidgets.blogspot.fr/2012/08/how-to-use-294-wxmsw-binaries.html


KariK


________________________________
 From: Dave Page <[email protected]>
To: Kari Karkkainen <[email protected]> 
Cc: Wahlstedt Jyrki <[email protected]>; Florian Klaar <[email protected]>; 
"[email protected]" <[email protected]> 
Sent: Sunday, February 10, 2013 4:40 PM
Subject: Re: [pgadmin-hackers] Problems building pgAdmin with wxWidgets 
binaries for Windows
 

You shouldn't need to touch the linker config - just use the non-2.9 build 
targets. If you're hacking config options, you're almost certainly doing it 
wrong.

Unresolved PQ symbols indicate you don't have either the PostgreSQL libraries 
installed (I'd suggest using the EnterpriseDB installer as we know that'll 
work), or you don't have %PGDIR% pointing to the installation.



On Sun, Feb 10, 2013 at 1:46 PM, Kari Karkkainen <[email protected]> 
wrote:

Hi,
>
>
>Thank you all, I'm making some progress. 
>
>
>I think I sorted out the 2.8 vs 2.9 issue (by removing all wxWidgets 2.9 
>libraries from "Additional Dependencies" under the Linker configuration), but 
>now I cannot figure out why I get a bunch of these types of linking errors: 
>"error LINKxxx: unresolved external symbol_PQxxx"
>
>
>I'm guessing these are maybe due to the PostgreSQL libbq.lib not being linked 
>with properly - any thoughts on this? 
>
>
>KariK
>
>
>
>
>________________________________
> From: Dave Page <[email protected]>
>To: Wahlstedt Jyrki <[email protected]> 
>Cc: Kari Karkkainen <[email protected]>; Florian Klaar 
><[email protected]>; "[email protected]" 
><[email protected]> 
>Sent: Sunday, February 10, 2013 3:21 PM
>
>Subject: Re: [pgadmin-hackers] Problems building pgAdmin with wxWidgets 
>binaries for Windows
> 
>
>
>In VC++ we have different build targets for wx2.9 (and, VC++ 2010 is supported 
>- I use it all the time - it's just the wxmsw build script that hasn't been 
>updated recently).
>
>
>
>On Sun, Feb 10, 2013 at 7:42 AM, Wahlstedt Jyrki <[email protected]> wrote:
>
>Hi,
>>in configure phase (on other platforms, I haven't looked at Windows) there is 
>>a setting:
>>    --with-wx-version=2.9
>>
>>
>>If you can find something similar, that might help.
>>
>>
>>On 10.2.2013, at 9.12, Kari Karkkainen <[email protected]> wrote:
>>
>>Hi Florian,
>>>
>>>
>>>Thanks a lot for your quick and detailed response.
>>>
>>>
>>>Yes, I followed those pgAdmin building instructions from the INSTALL file. 
>>>But I struggled (including discovering that vcbuild has been replaced with 
>>>msbuild with incompatible switches...) with that stuff for a couple of days 
>>>and gave up, and was hoping the wxWidgets binaries+headers would be the way 
>>>to go. I am getting much further with this approach but still failing at the 
>>>end.
>>>
>>>
>>>I'm using Visual Studio 2010 Professional (running on 64bit Win 7); not sure 
>>>if that is a problem. I have noticed that at wxWiki 
>>>(http://wiki.wxwidgets.org/Microsoft_Visual_C%2B%2B_Guide) they recommend 
>>>using VC++ 2008 Express edition which, as you pointed out, is not so easy to 
>>>find anymore. 
>>>
>>>
>>>But as I said, currently my build fails since 'wxbase28u.lib' is not there. 
>>>However, 'wxbase29u.lib' is there (because I'm using the 2.9.4 binaries, I 
>>>assume), but I just don't know why the linker is looking for the 28 version 
>>>and not the 29 version, and how to change this...
>>>
>>>
>>>KariK
>>>
>>>
>>>
>>
>>
>>
>>!! Jyrki Wahlstedt
>>!http://www.wahlstedt.fi/jyrki/
>>!
>>! Our life is no dream; but it ought to become one and perhaps will.
>>! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0  A780 6366 
>>EFD9 139C C386
>>
>>
>> 
>>
>
>
>
>-- 
>Dave Page
>Blog: http://pgsnake.blogspot.com
>Twitter: @pgsnake
>
>EnterpriseDB UK: http://www.enterprisedb.com
>The Enterprise PostgreSQL Company
>
>
>


-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Reply via email to