You can check this plugin https://github.com/obfuscated/cb_gdbmi for an example how to implement an autotools based build system for your plugin.-> My work for this week.
p.s. What are these cci and hhi files?cci = c++ code include file
p.p.s. If you ask me the code is close to unreadable with all this aligning that you're using.I read other's code with difficulty because all seems scattered...
Why not use the standard .h and .cpp files?p.s. What are these cci and hhi files?cci = c++ code include file
hhi = c++ header include file
only 3 (big) files in which the .cci and .hhi files are included are compiled.
It's a ( bad ? ) habbit
#include "sdk.h" // Code::Blocks SDK
// ............................................................................
#ifndef CB_PRECOMP
#include "manager.h"
#include "configmanager.h"
#include "configurationpanel.h"
#include "editormanager.h"
#include "projectmanager.h"
#include "logmanager.h"
#include "editorbase.h"
#include "cbeditor.h"
#include "sdk_events.h"
#include "misctreeitemdata.h"
#include "cbworkspace.h"
#include "cbproject.h"
#include "projectmanager.h"
#endif
By the way,I haven't try it, since I normally does not use the standard OpenFilesList plugin yet.
- did you try it ? Found it useful ? I always wanted to have at least separators in the OpenFilesList plugin.
- what do you think is a simple way to track memory leaks in a C::B plugin ? How do you do ?
What memory leaks do you have?I dont know, I m searching for them
Just run it under GDB?No, valgrind but it takes hours, even when removing lots of C::B plugins
I made an enhanced version of the classic OpenFilesList plugin, called OpenFilesListPlus :
screenshot 1 (http://www.mediafire.com/view/5c6hlazxfg3hn78/presentation-features-001.png)
screenshot 2 (http://www.mediafire.com/view/32twxxgs23kx29f/presentation-features-002.png)
It is available on github here (https://github.com/earlgrey-bis/cb-OpenFilesListPlus)
Only for codeblocks versions >= svn revision 10502 - C::B compilation mandatory
Installation instructions are on the wiki (https://github.com/earlgrey-bis/cb-OpenFilesListPlus/wiki), but are only complete for Linux at the moment.
Feedback welcome on this thread.
( and thanx to the C::B team for having added my patch )
how insttal it
You can check this plugin https://github.com/obfuscated/cb_gdbmi for an example how to implement an autotools based build system for your plugin.
cpp -dM ./empty-file.hxx
#define __DBL_MIN_EXP__ (-1021)
...
#define unix 1
...
#define linux 1
...
#define __ATOMIC_RELEASE 3
@line 222 : const bool linux = (id == platform_linux);
@line 228 : const bool unix = (linux | freebsd | netbsd | openbsd | darwin | solaris);
Installation instructions are on the wiki (https://github.com/earlgrey-bis/cb-OpenFilesListPlus/wiki), but are only complete for Linux at the moment.BTW: You don't provide Windows project files. So many people will miss your plugin effort.
BTW: You don't provide Windows project files. So many people will miss your plugin effort.OK, I tried to make a Windows project file so I had to look into it.
BTW: You don't provide Windows project files. So many people will miss your plugin effort.I have not used ms products since years, but I got some skills in that ; unfortunately :
I am unable to compile a vc++ ( visual studio community 2015 ) solution of my plugin :Why would you want to do that? With Windows files I mean C::B project files that compile under Windows using (TDM)/GCC, of course.
That was maybe a misunderstandingYes - Anyway, I am relieved that I shall not have to deal with msvc ( and incidentally I fixed by MOOTMGR-is-missing pb )
BTW: You don't provide Windows project files. So many people will miss your plugin effort.Done, you can checkout the "pub" branch if you want.