Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Building Code::Blocks on Win 64
ironhead:
Sorry for reviving such an old thread, but is there any plans to incorporate the Win64 changes into Code::Blocks svn? I'm trying to compile it for my Win7 64-bit machine and hitting similar issues to those mentioned in this thread.
Thank you.
Biplab:
--- Quote from: ironhead on August 17, 2010, 02:27:28 pm ---Sorry for reviving such an old thread, but is there any plans to incorporate the Win64 changes into Code::Blocks svn? I'm trying to compile it for my Win7 64-bit machine and hitting similar issues to those mentioned in this thread.
Thank you.
--- End quote ---
Thank you for reviving this old thread! :)
The answer is Yes, it will be incorporated in SVN. I was waiting for the new release. Now as the release process is over, I'll commit those changes to trunk. But it will take some time. At least I target committing major portion of patch to trunk within few months. There are few things holding me at the moment.
1) I am using WPG-System64 to compile C::B under Windows 64. However I believe WPG-System64 project is currently unmaintained and I would like to move to MinGW-w64 released builds. However if I use MinGW-w64 compiler C::B compiles fine; but it crashes when I try to run it. GDB also doesn't give crash report. If I can't resolve that I may need to stay with WPG-System64 compiler unless I find some suitable alternative.
2) I still could not figure out a good way to resolve hang-on-exit bug. This is a major blocker for us at the moment.
Any help in this regard is appreciated. :)
oBFusCATed:
--- Quote from: Biplab on August 17, 2010, 03:10:35 pm ---2) I still could not figure out a good way to resolve hang-on-exit bug. This is a major blocker for us at the moment.
--- End quote ---
This could be related to this:
http://forums.codeblocks.org/index.php/topic,10908.msg87337.html#msg87337
Also on linux I get this crash:
--- Code: ---(gdb) bt
#0 0x0000000000000021 in ?? ()
#1 0x00007ffff7aa33a0 in wxPGGlobalVarsClass::~wxPGGlobalVarsClass() () from /usr/lib/libcodeblocks.so.0
#2 0x00007ffff7ab9508 in wxPGGlobalVarsClassManager::~wxPGGlobalVarsClassManager() () from /usr/lib/libcodeblocks.so.0
#3 0x00007ffff485aa25 in __cxa_finalize () from /lib/libc.so.6
#4 0x00007ffff7782556 in ?? () from /usr/lib/libcodeblocks.so.0
#5 0x0000000000000076 in ?? ()
#6 0x0000000000000000 in ?? ()
--- End code ---
This is related to the wxPG 1.4 and happens only when I build C::B with autotools sysmem.
billyonthemountain:
--- Quote from: Biplab on August 17, 2010, 03:10:35 pm ---If I can't resolve that I may need to stay with WPG-System64 compiler unless I find some suitable alternative.
--- End quote ---
Did you try with TDragon's multilib build of GCC ? It's not a native 64bit compiler but it should do the job until the issues with mingw-w64 have been solved...
@Biplab: I haven't seen vityan's updated patch on the tracker so I suppose your patch "64bit-13-01-10_v1" is still the last version ?
TDragon:
--- Quote from: billyonthemountain on August 17, 2010, 09:21:34 pm ---Did you try with TDragon's multilib build of GCC ? It's not a native 64bit compiler but it should do the job until the issues with mingw-w64 have been solved...
--- End quote ---
It's the closest thing to a native 64-bit compiler you're going to find. It's configured with build, host, and target system all assigned as x86_64-w64-mingw32. Even the MinGW-w64 project itself doesn't distribute a build with this configuration.
If the fact that the compiler binaries are 32-bit is causing problems for you, I'd definitely like to hear about it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version