www.embtechgroup.eu/cbe.jpg (http://www.embtechgroup.eu/cbe.jpg)...what do you want to tell us with this? Where is the official page, is it Open Source, does this "product" comply with GPL?
Do you have some comittee that approves these changes or better to create new branch ?The committee are we (the developers and the community). A new branch like the debugger branch is possible, whenever it makes sense. E.g. modifications of the core or core plugins where everybody would benefit.
I just want to ask how far is the time when your C::B turns into commercial edit ?
etg: It was communism not socialism :)
I think the license for the SDK is GPL 3, so if you distribute the plugin you should provide
the source to the person your are distributing the plugin (he/she can pay you for plugin, it is not forbidden by the license).
Probably this could shed some light: http://www.gnu.org/licenses/gpl-faq.html
/*
* This file is part of the Code::Blocks IDE and licensed under the GNU Lesser General Public License, version 3
* http://www.gnu.org/licenses/lgpl-3.0.html
Also, I think it is better to use a separate GDB rather than a custom library. This way you can build/get GDB for whatever target you are using rather than trying to adapt and recompile a custom library.
Does code::blocks use the GDB mi interface in the debugger branch? This would probably be better than the current stdin/stdout redirection method since it let's you interact with GDB while the debugee is running and you can stop individual threads.No, it uses the normal interface. I've a plugin that uses the MI interface but it is not very usable at the moment.
I just want to ask how far is the time when your C::B turns into commercial edit ?Basically it can't, as we setup the license not to allow this.
1. sounds line SOCIALISM past 20 years in eastern EUROPE where nobody owned nothing1.) ??? I don't get what you mean by that.
[...]
3. what are then the DONATIONS on your C::B page ?
I will provide the C::B::E + DEBUGGER PLUGIN for ARM NXP CORTEX M3 family development for download at right time when will be sure it is stable for user.That sounds reasonable. Without looking at it it'll be hard to say how easy it can be integrated.
Going to gdb/mi would be better for embedded targets. In my cbmcu plugin I have to issue a "halt" command via openOCD to halt execution. I have not found a way to do this via the current exec method.oBFusCATed has fixed things in the debugger branch so that you can halt remote targets on Windows. He has it send a console break event to the gdb console process.