User forums > Help
wxPack and cannot find -lwxmsw_core
SedesGobhani:
--- Quote from: stahta01 on August 18, 2009, 03:41:12 pm ---Shot in the dark, is your file extension correct?
.c for c code
.cpp for c++ code
Tim S.
--- End quote ---
I am actually not using any of my own stuff yet. This is just files from the Code::Blocks wizard for the starter wx dialog app. They were probably pretested and I doubt the problem could be there.
Regarding the compiler that wxPack was compiled with, I'm not sure how I would know. There are libraries precompiled in something. There are lots of makefiles for different compilers in the pack.
A little research seemed to indicate it may have something to do with something called an "unwinder" which is not in the main lib but in some secondary lib, but I don't know what lib that would be. Bottom line seems to be since I don't know how wxPack was compiled, and I don't know what I was doing the first time I compiled wxWidgets, I'm going to have to bite the bullet and recompile it (like 3 hours d'oh!).
I have been looking for documentation on mingw compiler/linker options but haven't been able to locate in the MinGWiki pages. That's probably a big source of my problem. Anyone have a pointer to that? I see lots of examples with different options being used but I can't find them all in one place with documentation. I bet some make-file genius knows.
Thx,
SG
SedesGobhani:
--- Quote from: SedesGobhani on August 18, 2009, 07:40:53 pm ---
--- Quote from: stahta01 on August 18, 2009, 03:41:12 pm ---Shot in the dark, is your file extension correct?
.c for c code
.cpp for c++ code
Tim S.
--- End quote ---
I am actually not using any of my own stuff yet. This is just files from the Code::Blocks wizard for the starter wx dialog app. They were probably pretested and I doubt the problem could be there.
Regarding the compiler that wxPack was compiled with, I'm not sure how I would know. There are libraries precompiled in something. There are lots of makefiles for different compilers in the pack.
A little research seemed to indicate it may have something to do with something called an "unwinder" which is not in the main lib but in some secondary lib, but I don't know what lib that would be. Bottom line seems to be since I don't know how wxPack was compiled, and I don't know what I was doing the first time I compiled wxWidgets, I'm going to have to bite the bullet and recompile it (like 3 hours d'oh!).
I have been looking for documentation on mingw compiler/linker options but haven't been able to locate in the MinGWiki pages. That's probably a big source of my problem. Anyone have a pointer to that? I see lots of examples with different options being used but I can't find them all in one place with documentation. I bet some make-file genius knows.
Thx,
SG
--- End quote ---
Well I had a few moments of joy as I did a clean workspace, added -mingw32-g++ to linker options, and rebuild workspace, and it actually compiled and linked. But when I ran it I got App error message: "The application failed to initialize properly (0xc0000005). Click on OK to terminate the application." The build messages also looked a bit odd:
...
Compiling: resource.rc
Compiling: fx2gui3App.cpp
Linking executable: bin\Release\fx2gui3.exe
Info: resolving wxDialogBase::sm_eventTable by linking to __imp___ZN12wxDialogBase13sm_eventTableE (auto-import)
Info: resolving _wxEmptyString by linking to __imp__wxEmptyString (auto-import)
Info: resolving _wxDefaultSize by linking to __imp__wxDefaultSize (auto-import)
Info: resolving wxStringBase::npos by linking to __imp___ZN12wxStringBase4nposE (auto-import)
&c...
C:\Program Files\CodeBlocks\MinGW\bin\ld.exe: warning: auto-importing has been activated without --enable-auto-import specified on the command line.
This should work unless it involves constant data structures referencing symbols from auto-imported DLLs.
Output size is 82.00 KB
&c...
oBFusCATed:
"The application failed to initialize properly (0xc0000005). Click on OK to terminate the application." is spitted by the visual studio/C runtime library (most likely).
I've seen that message when some of the libs/dlls are compiled with vc2005/vc2008 but the correct runtime is not installed/found.
Keep in mind that vc2005 runtime is different from vc2005sp1 runtime and from any other hot fixed runtime (there was a hotfix to the runtime :( ).
SedesGobhani:
I went back to my first wxWidgets build, and reran the wizard, telling it to use the DLL, and it worked!!! Compiled and linked and ran!
But now I have to drag this big DLL file along with my program, when I wanted the program to be stand alone, so I still need to recompile static. Crossing fingers!!!
Thanks folks for being patient with me through all this traumatic experience. :mrgreen:
SedesGobhani:
And it works!
(Now I feel stupid for all them bad things I thought about C::B).
SG
Navigation
[0] Message Index
[*] Previous page
Go to full version