The build instructions can be found in the qp-gcc - Project Hosting on Google Code
Seems need a English version for this. :DTrue. I don't think its going to be accepted otherwise.
Ok, I will translate the Chinese build docs to English version as soon as possible.Seems need a English version for this. :DTrue. I don't think its going to be accepted otherwise.
By the way, All the build work was done by Loaden, I just tested the release for several days.Some questions that would be nice to know:
I like it! thank you! I have a problem.You only need to recompile your project!
Do I have to rebuild all libs(such as wx, xerces-c, ...) with the Loaden's gcc? Those lib have been build by offical ming.
Yes, ollydbg test it. it's can be debug well.By the way, All the build work was done by Loaden, I just tested the release for several days.Some questions that would be nice to know:
- Does it compile wxWidgets?
- Does it compile things like boost?
- Does it compile Code::Blocks?
- Does it allow debugging into wxWidgets apps (like Code::Blocks, wx v2.8.10)?
- Does it allow debugging into wxWidgets versions >= 2.9.x apps?
yesBy the way, All the build work was done by Loaden, I just tested the release for several days.Some questions that would be nice to know:
- Does it compile wxWidgets?
- Does it compile things like boost?not tried yet
- Does it compile Code::Blocks?yes
- Does it allow debugging into wxWidgets apps (like Code::Blocks, wx v2.8.10)?yes, I can debug both exe and dll, cc plugin...
- Does it allow debugging into wxWidgets versions >= 2.9.x apps?not tried yet
bjam --build-type=complete threading=multi --libdir=".\lib" --toolset=gcc-4.4.3 stageconfigure -prefix D:\DengYC\LoveDEV\qt -debug-and-release -platform win32-g++ -shared -fast -opensource -no-qt3support -no-zlib -no-openssl -no-webkit -no-style-plastique -no-style-cleanlooks -no-style-motif -no-style-cde -nomake examples -nomake demos -nomake translationsI like it! thank you! I have a problem.You only need to recompile your project!
Do I have to rebuild all libs(such as wx, xerces-c, ...) with the Loaden's gcc? Those lib have been build by offical ming.
That is say : they have the compatible ABI ?Yes, I think so.
Hi, allI know that, and i will try it.
Do you know about MinGW-W64 project(http://www.sourceforge.net/projects/mingw-w64)? This project provides 32-bit/64-bit runtime library and also native/cross 32-bit/64-bit compiler.
Though it's not very urgent to port Codeblocks itself to 64-bit. But users may need to use Codeblocks to build 64-bit application. So I think, in the comming release, we could provide both MinGW and MinGW-W64 compiler.
I have successfully built the compiler from GCC 4.4.3/GCC 4.5.0 and MinGW-W64-CRT source(both 32-bit and 64bit), and also wxWidgets.
The Advantages:
1. 32-bit/64-bit support :D
2. Fully UNICODE support. that is with --municode link flag, the entry point will be wmain/wWinMain other than main/WinMain, just like MSVC.
3. TLS(Thread local storage) support. MinGW's runtime doesn't support this.
Throw this project is currently in beta now, but it's already very stable now. Downloadable binary is in its project page, the Win32/Win64 personal-build by sezero is recommanded.
seems that gcc 4.4.4 also released recentlyI know, and gcc 4.5.0 released too: http://qp-gcc.googlecode.com/files/mingw4.5.0.7z (http://qp-gcc.googlecode.com/files/mingw4.5.0.7z)
It is great.I have try, But i don't know how to implement it.
But it seem lost "-finput-charset=BIG5" parameter of mingw32-g++.exe .
Because I got this message " no iconv implementation, cannot convert from BIG5 to UTF-8", if I use "-finput-charset=BIG5".
Thank you for your reply.
But it seem lost "-finput-charset=BIG5" parameter of mingw32-g++.exe .
Because I got this message " no iconv implementation, cannot convert from BIG5 to UTF-8", if I use "-finput-charset=BIG5".