To build a CB plugin you'll need the CB sdk which you can
obtain by compiling the SVN source with the cbNightly.
But the "New Plugin" script also refers to the wxWidgets source. It asks for the values of Global varables "cb", "cb_release_type" and "wx".
By compiling CB, you'll have the "cb" variable that should point to the CB src folder.
Or just enter ]"$(COEBLOCKS\..)" for a value that already will resolve to the source folder.See:
https://wiki.codeblocks.org/index.php/Variable_expansionThe cb_release var should == "-g" for debugging.
But you'll need to compile wxWidgets 3221 to get the "wx" value.
This older URL explains the source installation of CB and wxWidets.
https://wiki.codeblocks.org/index.php/Installing_Code::Blocks_from_source_on_WindowsBut it's a bit outdated for wxWidgets 3221.
To compile wxWidgets 3221 I use the following compile command in a .cmd file:
:DoClean
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb CXXFLAGS+="-std=c++11" clean
:DoCompilesOnly
mingw32-make -f makefile.gcc SHARED=1 MONOLITHIC=1 BUILD=release UNICODE=1 VENDOR=cb CXXFLAGS+="-std=c++11"
Note that when using the "File/New/CB plugin" script, your plugin output ends up in the devel32 folder
( $(#cb)\devel32\share\codeblocks\plugins\ )
whereas CB on Windows looks for plugins in the devel32_64 folder. So you need to change the output destination or copy the plugin dll to the correct folder.
Hope this helps.
Edit: After testing the "New CB plugin", I see that $(CODEBLOCK) is pointing to a folder with no source (namely the nightly).
The script will get a linker error which can be resolved by adding "$(CODEBLOCKS)" to the seach directory for the linker.
Recent Posts