User forums > Help

Linker Error!!!

<< < (2/2)

stahta01:
NOTE: Confirm you set the wx global variable correctly under Global Variables.
Confirm you used it right also.

The following is NOT normally the correct thing to do.

--- Quote ---I've also setup the wx/Lib to point to C:\wxWidgets-2.8.12\lib\vc_lib.

--- End quote ---


IF Global Variable is right your config is likely wrong.

I suggest renaming your code::blocks config file and trying to setup Code::Blocks again to use MSVS.

Under %APPDATA%\codeblocks standard name is default.conf
Must NOT be Running Code::Blocks when renaming or deleting config file.

Tim S.

pabon:
My intial global variable was set at: wx base = c:\wxWidgets-2.8.12. I only included the 'include' directory as one of my many steps to troubleshoot the link /LIBPATH error. I figured out why I'm getting the link /LIBPATH error. It has to do with my project build option linker-libraries setting that are being entered automatically by C::B. I'm using a unicode build of wxWigets. C::B had the link libraries setting like so:

link libraries
     are             should be
   wxmswd          wxmsw28ud
   wxbased          wxbase28ud
    etc..                etc..

I am now getting alot of:
 TutorialMain.obj||error LNK2019: unresolved external symbol "void __cdecl wxOnAssert(char const *,int,char const *,char const *,char const *)" (?wxOnAssert@@YAXPBDH000@Z) referenced in function "public: __thiscall wxStringBase::wxStringBase(class wxStringBase const &)" (??0wxStringBase@@QAE@ABV0@@Z)|
errors. I'm going to follow your suggestion and rename my default.conf file and see if I can reconfigure c::b.

Thanks for your help Tim.

Pabon

pabon:
SUCCESS!! Finally.

For whatever reason, on my first attempt to set the wx global variable, C::B would not accept my location for wxwidgets (which was valid). And the wizard would prompt me to enter it again. In both cases I used the browse button in the project wizard to set the variable. On the second attempt in would accept it, but would put the literal directory string in the wizards wx variable text block, as opposed to referring to $(#wx).

And for some reason with the literal directory set for the wx variable, the project wizard would not display the configuration page that allows for the setting of the wxwidgets build configuration e.g.  static, monolithic, unicode, etc. Once I had the ability to make those setting everthing worked. After changing the literal directory location with the $(#wx) variable string.


Thank you Tim.S for all your assistance.

pabon

Navigation

[0] Message Index

[*] Previous page