Development of the CodeBlocks plug-in (1)-Introduction

CodeBlocks + wxWidgets + wxSmith + Plugin, and cross-platform at the same time, this development method will surely be fascinating to you!

This article briefly describes how to develop a CodeBlocks Plugin:

0. environment of this Article

Codeblocks-10.05mingw.exe Codeblocks-10.05-src.tar.gz wxPack-2.8.10.06.exe

1. Create a project. Select Code: Blocks plugin as the type.

2. Enter the basic information and select wxWidgets 2.8.x.

3. The important variables to be set are wx and cb. We all know that the wx variable is the wxWidgets directory. After wxPack is installed, you can get

The cb directory refers to the codeblocks sdk directory. codeblocks does not have an sdk and codeblocks plug-in development. The basic method is to use the header file of the codeblocks source package + the library of the binary Package.

The certificate plug-in will not fail to load because of incomplete symbols.

4. Install wxPack and decompress the source code of codeblocks.

5. After the default project settings are compiled successfully, if the plug-in loading fails, for example:

The author's experience is that wxPack is used to decompress the wxWidget library. In this case, it is convenient to make the plugin use the wxWidget library used when codeblocks is running, in this way, the symbols are not uniform or cannot be found.

You can set it as follows:

You can edit wxmsw28u in Build options> Liker setting> Like library and point to the wxWidgets library used by CodeBlocks in the codeblocks installation directory, such as wxmsw28u_gcc_cb.dll.

6. if you do not need the 5 method, you can replace the wxWidget library so that the Library is exactly the same as the library currently used by codeblocks, or let the plugin put different libraries. a is completely connected. Of course, the 5 method is the best.