Re: Problems building pgAdmin with wxWidgets binaries for Windows
От | Dave Page |
---|---|
Тема | Re: Problems building pgAdmin with wxWidgets binaries for Windows |
Дата | |
Msg-id | CA+OCxowQi3Rgq6ewZASZcam295WuTKii1u4hpMFYm7zduzpkcw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Problems building pgAdmin with wxWidgets binaries for Windows (Wahlstedt Jyrki <jwa@wahlstedt.fi>) |
Ответы |
Re: Problems building pgAdmin with wxWidgets binaries for Windows
|
Список | pgadmin-hackers |
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 <jwa@wahlstedt.fi> wrote:
Hi,in configure phase (on other platforms, I haven't looked at Windows) there is a setting:--with-wx-version=2.9If you can find something similar, that might help.On 10.2.2013, at 9.12, Kari Karkkainen <kari_karkkainen@yahoo.com> 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!! 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
В списке pgadmin-hackers по дате отправления: