Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Building Code::Blocks on Win 64
ironhead:
--- Quote from: Biplab on August 17, 2010, 03:10:35 pm ---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.
--- End quote ---
Excellent, I look forward to beta testing it! ;)
As TDragon mentioned, his TDM-GCC is excellent. It's based on MinGW-w64 and produces native 64-bit binaries. If you are looking for a native 64-bit gcc, I've also come across this: http://code.google.com/p/mingw-w64-dgn/.
Cheers!
Chris
Biplab:
--- Quote from: oBFusCATed on August 17, 2010, 03:25:11 pm ---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.
--- End quote ---
I'll check that thread. Thanks for the pointer. However the bug I'm mentioning is not wxPG related.
--- Quote from: TDragon on August 17, 2010, 09:36:51 pm ---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.
--- End quote ---
I have not tried TDM-GCC 64 bit compiler. The issue is not that the compiler binary is 32 bit; issue is resulting C::B 64 bit binary doesn't run. It crashes at startup and GDB doesn't show any useful information. I'll give TDM-GCC a try.
--- Quote from: billyonthemountain on August 17, 2010, 09:21:34 pm ---@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 ?
--- End quote ---
I had posted another patch on 29/may/2010. That patch is also attached with this post.
If my current build (with wx-2.9.1) is successful, I'll post another patch.
--- Quote from: ironhead on August 18, 2010, 03:22:01 am ---
Excellent, I look forward to beta testing it! ;)
As TDragon mentioned, his TDM-GCC is excellent. It's based on MinGW-w64 and produces native 64-bit binaries. If you are looking for a native 64-bit gcc, I've also come across this: http://code.google.com/p/mingw-w64-dgn/.
--- End quote ---
Thanks for the pointer. I'll try them in future.
If my current build successful I'll upload a new binary. You can try that! :)
Edit 1:
Old Patch attached.
Biplab:
I've uploaded a new test build to the following link.
--- Quote ---http://www.box.net/shared/qkjyd2yldy
--- End quote ---
Patch needed to build this is attached with this post.
Please note-
1) hang-on-exit bug is still there. You need to kill it using Task manager.
2) If this build crashes while opening a project / file, disable "Code Completion" plugin and then try again.
3) This build includes only Core plugins.
billyonthemountain:
--- Quote from: Biplab on August 18, 2010, 06:01:33 pm ---1) hang-on-exit bug is still there. You need to kill it using Task manager.
2) If this build crashes while opening a project / file, disable "Code Completion" plugin and then try again.
--- End quote ---
Ok I did some quick and dirty testing :
=> opening codeblocks (core) project file and contrib plugins workspace causes the application to crash. disabling Code Completion plugin effectively solves the issue. (as mentioned)
=> buling codeblocks (w/ contrib plugins) using the command line works properly. The hang-on-exit bug doesn't apply in this case.
=> running codeblocks in safe mode still harbors the hang-on-exit bug.
I will try to make use of this build for my upcoming project. Will post feedback as I encounter issues.
regards, Billy
ps: I was wondering if the dumpfiles windows provides for crash reports could be of any use... If needed I'll post them too.
Biplab:
--- Quote from: billyonthemountain on August 26, 2010, 03:36:26 pm ---ps: I was wondering if the dumpfiles windows provides for crash reports could be of any use... If needed I'll post them too.
--- End quote ---
Please post them. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version