Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: Roman on October 31, 2006, 06:57:46 pm
-
Is anyone aware of will mingw4.x be widely deployed and when if it does?
Best Wishes
Roman
-
I hope they've seriously improved the linker (slow) and hopefully filesizes generated by it are way lower :/
-
I hope they've seriously improved the linker (slow) and hopefully filesizes generated by it are way lower :/
Me too. :D
-
don't put your hopes up, I think it's gonna last for another long time.
And fixing their crash on 64bit is also no priority. 64-bit seems to sound to "futuristic" to them :-( :-( (a little bit disappointed)
-
don't put your hopes up, I think it's gonna last for another long time.
And fixing their crash on 64bit is also no priority. 64-bit seems to sound to "futuristic" to them :-( :-( (a little bit disappointed)
You broke my heart. :-( Developing without a debugger is no fun.
-
I didn't , they did. I have the same problem, bought a couple on months ago, a nice new pc, 64-bit dual core, lot's of ram, lot's of HD diskspace and I can't debug on windows with gdb :-( :-( :-( :-(
-
I didn't , they did. I have the same problem, bought a couple on months ago, a nice new pc, 64-bit dual core, lot's of ram, lot's of HD diskspace and I can't debug on windows with gdb :-( :-( :-( :-(
Hmm I have a 64-bit processor too, but I have a 32-bit version of Windows. I'm guessing you use the 64-bit version of Windows????
-
yes WinXp 64bit
-
yes WinXp 64bit
2 choices:
a) use vc compiler with cdb / win 64 bits
b) use gcc compiler with gdb / linux 64 bits
:P
-
Well, from what you're expecting what would be really needed is an improved version of ld, which is part of binutils. Now, about the file size for C++ programs, the only way to reduce it would be creating DLLs of libstdc++ or trying to use a recent version of msvc*.dll, but both approaches are problematic, and GDB is another piece of software too.
It seems GCC 4.x will take some time to be supported by MinGW. The release of 4.2.0 is getting close and I have my doubts MinGW release it... but I think I'll do :wink:
-
Well, however things seem to become better. For GCC 4.3 mingw was added as a secondary plattform (http://gcc.gnu.org/ml/gcc/2006-09/msg00368.html ), which means that the devs will now put serious effort in the mingw-version of the gcc. According to http://gcc.gnu.org/gcc-4.3/criteria.html :
Our release criteria for the secondary platforms is:
* The compiler bootstraps successfully, and the C++ runtime library builds.
* The DejaGNU testsuite has been run, and a substantial majority of the tests pass.
Which as i understand it means that "GCC 4.3 will only be released once it runs on every secondary platform". As MingW is now a secondary plattform, i guess we can expect MingW 4.3 to come out as soon as GCC 4.3 will be released (Which might still take some time, i'm guessing Februrary/March 2007: http://gcc.gnu.org/develop.html#timeline ).
-
Sadly I will have to abandon C::B and go back to visual studio. The lack of debugger on x64 is too painful. I would pay someone to fix it for me, but they must be small group who could.
-
Sadly I will have to abandon C::B and go back to visual studio. The lack of debugger on x64 is too painful. I would pay someone to fix it for me, but they must be small group who could.
have you tried using the visual studio compiler and cdb, but inside C::B?
-
I am using non official mongw gcc 4.1.1 that you can find there: http://oss.netfarm.it/mplayer-win32.php. I use gcc in scientific programming to be sure that my program is cross platform. Both gcc 4.1.1 and vc2005 give for me after all optimizations the same fast code, which is about 10% faster then I heve with mingw gcc 3.4.5. The only one problem - code generated be that version of gcc 4.1.1 is larger 15% then with gcc 3.4.5 and twice large than with vc2005 :?. The same code, compiled under linix suse works 20% faster :shock:.
In my project I use wxWidgets and everything was compiled without any problems even with widgets compiled with gcc 3.4.5.
Also I tested nonofficial mingw gcc 4.2.0. That should have openMP support but in nonofficial version it is no supported. Meanwhile, I saw tiles from openMP in mingw gcc 4.2.0.
Finally, have fan with nonofficial versions :D.
-
I also found that binaries seem to be a tad bit bigger with GCC 4.1.1, but they sometimes can also compress better with upx :D
-
Thanks Grom, that GCC 4.1.1 works great! I had to compile wxWidgets with 3.4.5 though, but it builded C::B successfully with 4.1.1 . I wrote a little script that toggles between the two versions whenever I needed them... Ceneza's Idea somewhere. Works great.
Official MingW support in GCC 4.3 hey ? Nice :)
Wonder if GDB will do something like that a few months after that as well, here is hoping :o
-
What options are you using with GCC 4.1.1 to get better control of warnings when compiling c++ code?
Tim S
-
My question is about gfortran support. I can compile gcc and g++ successfully, but I find compile gfortran fails. There is a bug in the code. But if I want to use g++, I must set the CPLUS_INCLUDE_PATH environment.
-
Which warnings, the warnings with building C::B or general warnings?
-
Which warnings, the warnings with building C::B or general warnings?
The warning from g++? Or at least that is my guess.
example warning when building C::B
C:\wx\inno\wxWidgets-2.6_BRANCH\include\wx\sizer.h:31: warning: type attributes are honored only at type definition
Tim S
-
type attributes are honored only at type definition
As far as my understanding goes... those are wxWidgets' warnings and not C::B warnings...
And they are even there when building wxWidgets with 3.4.5 (Or at least for me...)
EDIT: Look what Mandrav said about the warnings: http://forums.codeblocks.org/index.php?topic=270.msg3572