#481 [ScriptedWizard] Update "plugin" script to make it debuggable

[bluehazzard]

This patch adds a target to the plugin script of the scripted wizard what is debuggable.

Also it fixes the missing tinyxml include directory

See a discussion here:
http://forums.codeblocks.org/index.php/topic,21713.msg147947.html#msg147947

[Teodor Petrov]

What does to_codeblocks mean?

[bluehazzard]

a target what copies the binary output directly to the development folder of codeblocks. This makes debugging the plugin easier/ possible
The default target creates a .plugin file what can be installed in codeblocks

all contributed plugins in the workspace use this technique. Also all plugins i see around use a target like this.
But the actual plugin wizard creates only a .plugin file. To debug this kind of plugin you have to uninstall and install the plugin every time you start the debugger or copy it by hand...

[Teodor Petrov]

Then it is better to document this in the wizard...

[bluehazzard]

What explain and where in the wizard?
Is the idea welcome?

[ollydbg]

OBF means you should add those comments in the wizard.script, so that people can understand what do those variables mean.

[bluehazzard]

ok, i added some comments to the code

[bluehazzard]

I have created a 3th version of this script what uses squirrel scripting to copy the files. This provides a platform/ bash shell independent way to copy files

[Teodor Petrov]

1. Why do you need to call RemoveCommandsAfterBuild? Just modify SetupTarget to not add them
2. --no-dde and --no-check-associations are windows only flags
3. No wx3.0 builds support, but I'm not sure it is needed...

[bluehazzard]

Ok, so i reworked the script future:
1) Remove wx2.6 support
2) Add support for wx3.0 and wx3.1, make wx2.8 default
3) Changes for the windows build:
3.1) remove -ansi compiler option
3.2) add -std=gnu++11 compiler option
4) Changes for unix:
4.1) add option to choose system default wx-config parameters
4.2) add --version command line parameter for the different versions of wx
5) Add target "to_codeblocks" to make the plugin debuggable (see the discussion top)
6) Move all target common compiler/linker settings to the project
7) Use platform independent squirrel scripting to copy files

This is tested and works without problems in windows.
I have tested it on linux and encountered following problems i am not able to fix by myself (no time, not the spirit to change my working build environment):
1) I dont use the "pkg-config --cflags codeblocks" for my codeblocks builds, so i have to set up paths and linker options by hand. I don't know if this script works with pkg-config
2) I was not able to start the debugger with codeblocks. Codeblocks terminated with code 0377. At the moment i have no idea why (missing libraries? )
3) If i set Project->Set program's argument->Host application to $(#cb)/devel30/codeblocks the debugger does not find the host application (the log shows a empty host application). If i replace $(#cb)/devel30/codeblocks with /absolute/path/to/codeblocks it works. Can someone on a linux system test this?

[Teodor Petrov]

Please continue discusisons and improvements here: http://forums.codeblocks.org/index.php/topic,21941.msg149651.html#msg149651

[Teodor Petrov]

Are we done with this ticket?

[bluehazzard]

yes, this should be done. At least on windows all works as expected. I can not test it on linux at the moment...