User forums > General (but related to Code::Blocks)
[solved] codeblocks 13.12 & wxWidgets 3.0 config, ld.exe cannot find -lwxmsw30u?
alfredfvj:
I apologize for the typographical error.
My link library looks like this:
lwxmsw32ud
libshlwapi.a
libversion.a
The first line has only one "l" at the start.
My project is a wxWidget 3.1x with wxSmith as GUI builder and Frame based as Appllication Type.
I did not alter any codes generated by the wizard. I just clicked Build and Run button and I got the error : ld.exe||cannot find -llwxmsw32ud|
I did an experiment and included the extra "l" in my Link Library and made it consistent with what the Builder is looking for. The first line now read like this:
llwxmsw32ud
The build error now reads like this:
||=== Build: Debug in ClicsCP (compiler: tdm64Compile) ===|
ld.exe||cannot find -lllwxmsw32ud|
||error: ld returned 1 exit status|
||=== Build failed: 2 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|
Now there are three l's ("lll") at the beginning.
As to whether I really want to use the Debug version of wxWidgets, the honest answer is I don't really know. I have a very novice understanding of wxWidgets (and Code::Blocks) to make a reliable judgement on that having been exposed to it for just a few days. At this stage, I am just evaluating wxWidgets and wxSmith of Code::Blocks for use in converting a very large legacy application written in MS VFP. From the little that I've seen from Google search, the controls of wxWidgets seem to resemble closely those of VFP. And wxSmith is close enough with the GUI IDE of VFP.
The application that I will be converting has a lot of complex nested iterations and from what I gathered from articles about wxWidgets, the Debug mode will be a useful tool in this type of application. This conclusion of course, is coming from a very little informed perspective and if I will just be exposing myself to undue difficulties, I can do away with the Debug mode. Can I have your opinion on this as well?
Again, thank you very much for your patience. Your reply will be greatly appreciated.
Miguel Gimenez:
Remove the leading 'l' and replace the wxWidgets's debug library with the production one. Write exactly this:
--- Code: ---libwxmsw32u.a
libshlwapi.a
libversion.a
--- End code ---
You do not need the debug version unless you intend to debug wxWidgets itself.
alfredfvj:
As you suggested, I created a new project without the Debug option. My Build Options now only has Release.
Under the Link Library I entered libwxmsw32u and got the error message:
ld.exe cannot find -lwxmsw32u
Next I tried libwxmsw32u.a and got the same error.
Then I tried including libshlwapi.a and libversion.a and still got the same error.
Is it possible that this is because I'm creating a wxWingets 3.1 project while my wxWidgets is version 3.2? The code:blocks wizard does not include the option to choose version 3.2. Does code::blocks nightly build version have this option? Or maybe I can just install a 3.1 version of WxWidgets.
I will try exploring these options tomorrow (it's getting late in this part of the world and I still have some work to finish).
Thank you very much for your help.
Miguel Gimenez:
--- Quote from: Miguel Gimenez on April 28, 2023, 05:48:01 pm ---Remember to put the path to the library in Search directories -> Linker
--- End quote ---
TeMaToS:
I had similar issue and spent a loooot of time to fix it and the answer was not found I was able to figure that out by myself.
The issue was related to usage of MinGW inside CodeBlocks folder when compiling project and for compiling wxWidgets I was used MinGW that was installed separately.
Hope that at least it will help someone with similar issue.
Also it is possible that newer/older version of MinGW is incompatible.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version