Building wxWidgets 2.8.6 linker error with VS2005

[untergasser at gmail.com]

Thanks for the fast reply. I have a brand-new visual cpp express, a
fresh of the installer wxwidgets 2.8.6 and ordered the batch install
as recomendet. I didnt move or edit anything and I have no other wx
installed. I thought the wxDevC++ made the problems and deinstalled
it, but still I get this error messages (several, but this is a very
typical one which makes the others redundant):

Creating library ..\..\lib\vc_dll\wxmsw28ud_core.lib and object ..\..
\lib\vc_dll\wxmsw28ud_core.exp
app.obj : error LNK2019: unresolved external symbol "protected:
virtual class wxString __thiscall
wxAppTraitsBase::GetAssertStackTrace(void)" (?
GetAssertStackTrace at wxAppTraitsBase@@MAE?AVwxString@@XZ) referenced in
function "public: virtual bool __thiscall wxApp::Yield(bool)" (?
Yield at wxApp@@UAE_N_N at Z)
appcmn.obj : error LNK2001: unresolved external symbol "protected:
virtual class wxString __thiscall
wxAppTraitsBase::GetAssertStackTrace(void)" (?
GetAssertStackTrace at wxAppTraitsBase@@MAE?AVwxString@@XZ)
msgout.obj : error LNK2001: unresolved external symbol "protected:
virtual class wxString __thiscall
wxAppTraitsBase::GetAssertStackTrace(void)" (?
GetAssertStackTrace at wxAppTraitsBase@@MAE?AVwxString@@XZ)
rendcmn.obj : error LNK2001: unresolved external symbol "protected:
virtual class wxString __thiscall
wxAppTraitsBase::GetAssertStackTrace(void)" (?
GetAssertStackTrace at wxAppTraitsBase@@MAE?AVwxString@@XZ)
utilscmn.obj : error LNK2001: unresolved external symbol "protected:
virtual class wxString __thiscall
wxAppTraitsBase::GetAssertStackTrace(void)" (?
GetAssertStackTrace at wxAppTraitsBase@@MAE?AVwxString@@XZ)
..\..\lib\vc_dll\wxmsw28ud_core_vc_custom.dll : fatal error LNK1120: 1
unresolved externals

Regards,

Andreas

On Nov 21, 5:38 pm, va... at wxwidgets.org (Vadim Zeitlin) wrote:
> On Wed, 21 Nov 2007 08:31:52 -0800 (PST) untergas... at gmail.com wrote:
>
> > So how can I solve the problem properly?? And were does it come from?
>
>  It comes from mismatch between the headers used to compile your
> application and the libraries used to link it. So to solve it you must
> ensure that you use the same headers that were used for the library
> compilation for the application build as well.
>
>  As the problem usually arises because of local changes (such as editing or
> moving setup.h), I can't be more precise because I don't know what exactly
> happened on your machine. But I'm quite sure that if you do a clean rebuild
> of everything (and if you have no other/older wx versions on your machine)
> everything will build *and* work correctly.
>
>  Regards,
> VZ
>
> --
> TT-Solutions: wxWidgets consultancy and technical support
>                http://www.tt-solutions.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wx-users-unsubscr... at lists.wxwidgets.org
> For additional commands, e-mail: wx-users-h... at lists.wxwidgets.org