#Code blocks for windows 10 64 bit how to#
#Code blocks for windows 10 64 bit software#
#Code blocks for windows 10 64 bit code#
#Code blocks for windows 10 64 bit free#

We're switching from MinGW to the MinGW-64 compiler and I'm supposed to be the guinea pig.

#Code blocks for windows 10 64 bit code#

My job is to set in a cubicle all day and mindlessly crank out code for already laid out out libraries and programs.

#Code blocks for windows 10 64 bit software#

While I really LOVE the MinGW compilers, this is one drawback that I often find with open source software is that it's usually poorly documented, and because the software is also most often different in user interface from commercial or mainstream software, its lack of documentation makes it that much more difficult. But I still can't figure out the proper folders to list for the compiler, linker, and resource compiler under the 'Search directories' tab. m32 is for 32-bit compilation and -m64 is for compiling 64-bit programs. However, a switch is require to be placed in the 'Other options' sub-tab beneath 'Compiler settings'. Okay, after a bit more research on the MinGW site, here is what I've found:īoth 圆4 and x86 compilation will use the same executables.

#Code blocks for windows 10 64 bit free#

Remember, when it comes to compilers I'm pretty much an airhead, so feel free to explain it to me like a child, and pictures are more than welcome. I'm not sure if it makes any difference as far as the MinGW-64 folder structure is concerned, but I will be using the Windows API for GUI programming instead of wxWidgets.

#Code blocks for windows 10 64 bit how to#

But until then, can someone PLEASE explain to me how to properly configure my compiler setting profiles for both 32 and 64 bit console/Windows GUI programming in standard C++. Hopefully, Code::Blocks will include pre-configured settings for MinGW-64 in its next release. Each time someone tells me that I need to include these folders or that executable another person will then come along to contradict them, stating that I need these folders or that executable instead, and I don't know who is correct. I've raise this same issue on other boards. So, sadly I'm left more confused than when I started. However, I personally find their documentation to be vague and of poor quality and writing style. I've googled many examples for setting up this compiler with Code::Blocks and have tried using the documentation from the MinGW site. I've noticed that with each progressive version release of MinGW-64, the folder structure keeps changing, so looking at older examples doesn't help me at all. The folder/directory structure and naming scheme for MinGW-64 is very confusing and makes no logical sense to me. I also need these same questions answered for the 圆4 profile, because I know that often a person must utilize different headers and library files for 64-bit compilation as those for 32-bit programs. which executables do I list for the 'Program Files' sub-tab under 'Toolchain executables'? which folder(s) do I list for the 'Compiler' sub-tab under 'Search directories'?Ĥ. which folder(s) do I list for the 'Linker' sub-tab under 'Search directories'?ģ. which folder(s) do I list for the 'Compiler' sub-tab under 'Search directories'?Ģ.

I know basically how to create each setting profile, but I don't know the correct info to include in each profile - most specifically, those under the 'Search Directories' tab and the 'Toolchain Executables' tab.ġ. I want to create two separate compiler setting profiles:ġ.) 'MinGW-64 (GNU GCC) x86 Compiler' for 32-bit programs 2.) 'MinGW-64 (GNU GCC) 圆4 Compiler' for 64-bit programs I'm wanting to graduate from the included 32-bit MinGW and I am trying to setup MinGW-64 v4.9.0.2 to use with Code::Blocks on 64-bit Windows 8.1. If the compiler isn't already pre-configured in the IDE, I'm pretty much screwed. I have good experience with 64-bit programming, just not so while using either Code:Blocks or MinGW-64. Even though I'm pretty good at coding, when it comes to setting up compilers to use with an IDE, I tend to be an absolute airhead. Right off the bat, this is NOT an an error of any sorts with Code::Blocks, it has more to do with my own incompetence.