User forums > Help

wxWindows-2.4.2 problem....

<< < (2/2)

Matroc:
well, yeah i can reproduce them, importing the wx.dsw causes hundrets of them for me...

//edit
i just noticed: importing the wx_dll.sln file is even worse, it seems to try to read a null pointer somewhere, crashing c::b immediately (can be reproduced too ;-)

David Perfors:
I can't reproduce it... or should I try to compile first? I tried the wx.dsw. (with C::B 1.0finalbeta, Mingw, Windows XP.) I can't try that sln file, because I don't have it.

Anonymous:
Resolution was simple, as mandrav said it was enough to set compilers resource directories and wxWidgets is building. But when i try to link it with my own program i get few hundreds linker errors about unresolved external symbols (for example Mutex::Unlock(void)).

rickg22:
Matroc: Null pointers are EASY to diagnose! :D Run codeblocks in "debug mode" and wait for the segfault. Then do a backtrace and paste the results in a new bug report.

Navigation

[0] Message Index

[*] Previous page