ld.exe||cannot find -l||=== Build: Release in app1 (compiler: GNU GCC Compiler) ===|
ld.exe||cannot find -lwxmsw30u_core|
ld.exe||cannot find -lwxbase30u|
||error: ld returned 1 exit status|
||=== Build failed: 3 error(s), 0 warning(s) (0 minute(s), 0 second(s)) ===|
|
mingw.org, MinGW64 32 bit, or MinGW64 64 bit ?The compiler used by codeblocks is mingw32 as it was setup from its web installer with gcc version 4.9.3.1 or at lest I'm hopping the autodetect worked correctly.
GCC version of Compiler
Did you self-build wxWidgets?I used the wxWidget 3.1 and 3.0.2 installer for windows tried to use mingww32-make and failed to build wxwidgets repeatedly, my main problem was that the compiler could not find headers like stdio.h. After a day or two trying to find any information on how to set up any environment variables that might be needed I gave up and downloaded and installed TDM-gcc-32.
Are you using the CB Wizard? The CB Wizard is likely broken for wxWidgets 3.1.I have no idea what that is, so I have to say no at this time.
If using Cygwin GCC or MSys2 GCC, please state that. These need special methods to work with Code::Blocks.As far as I understand so far, I have not used any of those, although some msys package where installed by the mingw32 installer. I do not plan to use any unix like environment at all I prefer things as close to default installation as possible.
Do you plan to use wxSmith or wxFormBuilder?Yes I'm planning to use both of them at first until I settle down on a favorite. So far I think I only used wxSmith and I had an acceptable experience although at some point what ever I placed on it was resize to fill the complete form. So far I prefer the frames over the dialogs design, then again I have to run a couple of sample and see how it behaves before deciding.
If yes, which one?
This CB FAQ might answer your question; but, you likely will have more questions.Thank you, I will take a close look on that.
MinGW-TDM versions 4.9 and 5.1 (with the default SJLJ exceptions propagation method, using C++11).
I see at least a half dozen possible errors you might have made.Good! half a dozen is a manageable amount of errors. If you be so kind to name them so I can start working on them and see what I can come up with that would be grate.
But, the main one is I have no Idea what C++ Compiler you are really using; and, I do NOT think you know either.True! But I made sure that my path variable references only one installation at all times which did not help at all. I have tried to remove all references from the path as well calling the mingw32-make utility using the complete path which failed too. Just for the sake of it I opened the TDM shell and got the compiler version from there so here are the results.
C:\wxWidgets-3.1.0\build\msw>g++ -vAm I correct to assume that the compiler version 5.1.0?
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=C:/TDM-GCC-32/bin/../libexec/gcc/mingw32/5.1.0/lto-wrapper.exe
Target: mingw32
Configured with: ../../../src/gcc-5.1.0/configure --build=mingw32 --enable-languages=ada,c,c++,fortran,lto,objc,obj-c++ --enable-libgomp --enable-lto --ena
ble-graphite --enable-libstdcxx-debug --enable-threads=posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-threads
--enable-libstdcxx-time --with-gnu-ld --disable-werror --disable-nls --disable-win32-registry --disable-symvers --enable-cxx-flags='-fno-function-sections -fno
-data-sections -DWINPTHREAD_STATIC' --prefix=/mingw32tdm --with-local-prefix=/mingw32tdm --with-pkgversion=tdm-1 --enable-sjlj-exceptions --with-bu
gurl=http://tdm-gcc.tdragon.net/bugs
Thread model: posix
gcc version 5.1.0 (tdm-1)
I will see if I can write up some newbie style directions that use the wxWidgets built binaries because I think that is a major stumbling block for newbies.Well that is one way to go but it will not work for me. My ultimate goal is to set up a cross compilation environment to allow me to use windows as a developing environment for every target I might need.
No idea how many days this will take me. You will have to download an TDM GCC Compiler to match the wxWidgets 3.1.0 built binaries.Well can I have a couple of pointers that will allow me to work my way up? The idea is that I learn by solving using your hints as guides and in the process learn more than solving the specific problem. I know it looks counter intuitive but its my way of learning.
From https://github.com/wxWidgets/wxWidgets/releases/tag/v3.1.0 (https://github.com/wxWidgets/wxWidgets/releases/tag/v3.1.0)As far as I understand it would be beneficial for both of us to point me to how the basics of the wizard mechanism work so I can troubleshoot my problem, that way I will be able to help in some small way as well hopefully freeing you some time to spend on more interesting things.QuoteMinGW-TDM versions 4.9 and 5.1 (with the default SJLJ exceptions propagation method, using C++11).
I will see if the directions can support wxSmith; might try wxFormBuilder if I secede in getting wxSmith working.
I will be using an wx-config.exe to set most of the wxWidgets setting in Code::Blocks.
I have plans to add an option to the CB Wizard to use wx-config.exe in the future.
I strongly recommend newbies have only one MinGW GCC based compiler installation on their computers they can interfere with each other!Yeah I heard about that. Searching the net I see only generic statements and nothing to point in the problem it self ee config xxx is global or environment variable xy need to point to what ever. The problem is that not knowing how to validate the installation it makes it impossible for me to learn how to find problematic configurations and that is more damaging than any lack of information could ever be.
Edit: I would NOT be surprised if wxSmith and wxFormBuilder are both partly (or mostly) broken with wxWidgets 3.1.That's OK, I'm here to learn how to validate code block installations what I need to look for and how to identify possible friction points. I'm not here to give me an executable that will do the work for me that would be grate and all but the moment you moved on to other projects, I would end up on the same position I'm now.
I will NOT be able to help you using wxSmith and wxFormBuilder; I am a newbie with both.
Since you are a newbie, do you have any reason why you are NOT using wxWidgets version 2.8 or 3.0 instead of version 3.1?Yes I could not build 3.0.2 in debug mode and still can't here is the result of my latest effort
I noticed you had issues building wxWidgets 3.0; is that the main reason you are trying the development version of 3.1.0?
Because if it is a issue building wxWidgets; I would suggest going with wxWidgets 3.0.2.
C:/TDM-GCC-32/lib/gcc/mingw32/5.1.0/include/c++/bits/c++0x_warning.h:32:2: error: #error This file requires compiler andIf that makes any more sense to you. I'd rather not go to older releases but if everything else fails I might give it a go.
library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++
11 or -std=gnu++11 compiler options.
#error This file requires compiler and library support for the \
^
In file included from ..\..\include/wx/string.h:46:0,
from ..\..\include/wx/any.h:19,
from ../../src/common/any.cpp:18:
..\..\include/wx/strvararg.h:350:18: error: 'is_enum' in namespace 'std' does not name a template type
typedef std::is_enum<T> is_enum;
^
..\..\include/wx/strvararg.h:354:54: error: 'is_enum' was not declared in this scope
enum { value = wxFormatStringSpecifierNonPodType<is_enum::value>::value };
^
..\..\include/wx/strvararg.h:354:68: error: template argument 1 is invalid
enum { value = wxFormatStringSpecifierNonPodType<is_enum::value>::value };
^
makefile.gcc:11370: recipe for target 'gcc_mswuddll\basedll_any.o' failed
mingw32-make: *** [gcc_mswuddll\basedll_any.o] Error 1
Yes I could not build 3.0.2 in debug mode and still can't here is the result of my latest effortCodeC:/TDM-GCC-32/lib/gcc/mingw32/5.1.0/include/c++/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and
library support for the ISO C++ 2011 standard. This support is currently experimental, and must be enabled with the -std=c++
11 or -std=gnu++11 compiler options.
#error This file requires compiler and library support for the \
You need to add the option "-std=gnu++11" or define HAVE_TR1_TYPE_TRAITS to build wxWidgets 3.0.2 or you can patch the wxWidgets bug that was posted on this site a while back.that helped me to build wxwidget with both environment adding the option
CXXFLAGS="-std=gnu++11"in the command line.
I forgot who posted it he suggested using the patch as the proper solution and he is right. Searching on HAVE_TR1_TYPE_TRAITS should find the patch on this sit.Now of to read up on the link provided, hopefully it will provide inside on why building a wxSmith application raises the same problem now.
Added link to the post with the link offsite http://forums.codeblocks.org/index.php/topic,20607.msg140165.html#msg140165 (http://forums.codeblocks.org/index.php/topic,20607.msg140165.html#msg140165)
Tim S.
I have made progress on fixing the wx-config.exe for mingw32-make builds.I have no idea how or where wx-config is used so I do not know how helpful it is, get some sleep. personally I have a lot of pocking around to do inside the IDE to see where things are and most importantly what they are. Too many options to work with it will take some time. I grepped inside the codeblocks directory and found out that the 28, 16, 30 are hard coded inside the wizard's code which 1) is a bit backwards with my own logic and 2) not easily patched.
So, I am going to work on that for a while. I removed code that I thought was NOT needed till I saw the problem.
Note: My fix likely breaks some of the nice but not needed features of wx-config.exe.
Edit: I really need to get some sleep. I have fixed the only the MinGW GCC for use with the wxWidgets team built binary.
The same type of changes should also fix it for Visual Studio; but, I have been up over 26 hours straight. I hope this insomnia goes away. Link to https://github.com/stahta01/wx-config-win (https://github.com/stahta01/wx-config-win).
I decided that making wxSmith projects is beyond me. I will put my effort into getting the CB wxWidgets Wizard to use wx-config.exe.
I will write up directions on how to use the CB Project I created with wxTeam built binaries when I feel better.
Link to the sample CB Projects https://github.com/stahta01/cb_projects_for_wxWidgets/tree/wxWidgets-3.1.0 (https://github.com/stahta01/cb_projects_for_wxWidgets/tree/wxWidgets-3.1.0)
Tim S.