On 4/8/2012 11:37 PM, rajeshwari b wrote: > I tried building wxWidgets 2.8.12 through Msys. That is, through Msys > shell, the TDM-GCC was accessed. The log is attached regarding the > commands given, configuration, and make.
I have never tried building wxWidgets in MSYS. However, I've heard it is supposed to be possible. Your mileage may vary. > Previously, i could build wxWidgets 2.8.12successfully through > TDM-GCC, which then was not accessible from Msys. Then, tried > compiling from TDM-GCC terminal which was again giving error. I didn't > save that log. *snip* > then, opened the TDM-GCC terminal, removed the wxwidgets2.8.12 and > then installed again, i have attached the log (file name: > compile_log_tdm-gcc) for that. This log appears incomplete -- I see no error messages. If you want to use the TDM64 version of TDM-GCC to build a 32-bit version of wxWidgets, you'll probably need to alter "makefile.gcc" according to what I noted in my post here: <http://forums.codeblocks.org/index.php/topic,12701.msg86317.html#msg86317>. Even without having done that, your command for the build is not doing what you think. Assigning different values to the same environment variable doesn't add to it; it is merely overridden by the most recent assignment. I recommend the commands referenced in the wxWindowQuickRef at <http://wiki.codeblocks.org/index.php?title=WxWindowsQuickRef>, with a couple of additions for your specific use case: mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=0 UNICODE=1 CFLAGS=-m32 CXXFLAGS=-m32 RCFLAGS="-F pe-i386" Cheers, John E. / TDM ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
