Do I just point it to the directory where wxWidgets is found?There is no "wxWidgets settings" inside Code::Blocks. You just need to setup your project options (compiler/linker) to the appropriate folders. C::B itself uses wxWidgets 2.6.3 internally but that usually shouldn't matter to you. What counts for you is against what you are compiling/linking.
Before all of this, when CodeBlocks asked where wxWidgets was it had this variable thing in the textbox... something like $(#wx) or something like that... But now it doesn't show up anymore...
ok. I did that but the same message appears anyway...
the error doesn't apper when I'm compiling... it happens when I'm trying to create a project... CodeBlocks Nightly Build September 7 2006, wxWidgets 2.7.0. Windows XP SP2 system.Please tell us the directory structure of wxWidgets -> where are the includes and where o you have the libs? Then please explain in detail what settings from the wizard you don't understand (or post a screenshot of the appropriate dialog). This will help us to explain.
C:\SourceCode\Libraries\wxWidgets2.7
$(#wx)\lib\gcc_
$(#wx)\lib\gcc_lib
comctl32
ole32
oleaut32
uuid
Fix is here. :)Nice job. I haven't tested it yet, but there are many problems with choosing vc as your compiler. To see all the steps required to get the wxWidgets wizard up to working condition with Visual C++ please look at the tutorial here (http://wxpack.sourceforge.net/Tutorials/CodeBlocksWxWizardVC).
http://developer.berlios.de/patch/index.php?func=detailpatch&patch_id=1465&group_id=5358
Zc:wchar_t-
(More information: This setting should be in the Compiler|Compiler Flags tab, but it isn't, so we are adding it manually.)
Ok, so what I want to do is use the release version non-unicode (cause I want compatibility for Windows 98 as well)... RJP will that configuration you show me allow me to use this version (the release non-unicode version) of the wxWidgets libs?Yes all you need to do is make sure the 'u' is off the link library name. (The 'u' stands Unicode)
wxmsw27u
wxmsw27