vc++6.0 IDE's engineering uses Code::Blocks to open, compile, and debug the ultimate configuration scheme

Introduction: Unexpectedly can use code::blocks to open, compile, Debug VC 6.0 project, feel very magical, through the configuration also let us further understand VC + + 6.0 compiler, connector, debugger. Many brothers asked if you can support the latest VS2008 and VS2010, in fact Code::Blocks has been configured to our custom compiler IDE environment, if we use VS2003---VS2010, can not be configured. Just because the vc++6.0 is not the default, so only to explore a set of practical solutions come out. Before we take a picture of the Code::Blocks support and the configured compiler support list (except vc++6), because I use the version is Code::Blocks 10.05, so VS2010 did not add in, after the version has been added:

has been looking for the reasons for the popularity of vc++6.0, in the computer industry with the rapid development of a very old compiler, can sweep the process of the 13 nature has its magic weapon. I feel the reason for the following reasons:

① start-up speed, account for small memory, ② compact size and generated files small, ③ compile faster;

The vc++6.0 version, as a classic, is hard to replace. But at present the more hot programming tools undoubtedly have to count Code::Blocks and CodeLite. Here are just a few features of Code::Blocks:

Code::Blocks Free Open Source (we can directly download to its source code), start fast, small size, multi-function, support syntax color eye-catching display, support code completion, support code folding, support code formatting, you can configure different compilers, to compile common project templates (VC class, QT classes are readily featured), and the plugin is rich in functionality. Favorite is the inside like notepad++ double-click a variable, the entire file inside this variable is highlighted. In short there are countless reasons to try Code::Blocks.

Heard that code::blocks unexpectedly can replace VC6.0, or VC6.0 the following works can be directly within the Code::Blocks to modify the compilation, debugging. Feel very magical, linked to a week to look at a lot of code::block posts. Finally the configuration succeeded. Here are the specific configuration requirements:

Three tools to be installed are: ①code::blocks 10.05 version ②VC + + 6.0 (why to install VC6 mainly want to use the compiler inside the cl.exe, linker link.exe, Resource Compiler Rc.exe, Microsoft program Maintenance Utility NM Ake.exe) ③windebug 6.7.005 (This is the most important to use in the installation directory of the debugger CDB.exe)

(1) Install Code::Blocks 10.05, very simple is to download the next down the road. Official website Installation Guide Http://wiki.codeblocks.org/index.php?title=Installing_the_latest_official_version_of_Code::Blocks_on_Windows,

The Chinese installation guideline given by the No-Magic brothers http://blog.csdn.net/akof1314/article/details/6603177

(2) Configure vc++6.0 compiler, linker, debugger website to give instructions in English http://wiki.codeblocks.org/index.php?title=Integrating_Microsoft_Visual_C_6_ With_code::blocks_ide

Configure the path to the debugger, linker, resource Compiler:

The following topics focus on the installation of the debugger Windebug 6.7.005: (http://msdn.microsoft.com/en-us/windows/hardware/gg463016)

After installation, log down the path C:\Program files\debugging Tools for Windows to add it to toolchain excuteables-->additional path ' s inside, and in compiler Settings, tick/md and/zi two items

To configure the debugger:

Configuring the compiler switch

Open Project:

The final debugging effect:

Thanks:

This post was completed thanks to the no-illusions brothers and R3000 brothers, whose reference URLs are as follows

http://blog.csdn.net/akof1314/article/details/6603177

http://blog.csdn.net/r3000/article/details/5683431

http://blog.163.com/modingfa_002/blog/static/110925466201033091819425/

vc++6.0 IDE's engineering uses Code::Blocks to open, compile, and debug the ultimate configuration scheme