Hi André 
Am Dienstag, 31. Dezember 2013, 02:51:09 schrieb André Pönitz:
> Old story, next attempt: For Creator 3.1 I'd like to discontinue
> support for GDB builds that do not have Python scripting enabled.
>
> This will allow for removal of almost 2/3 of the GDB specific parts of the
> debugger plugin including the compiled variety of the debugging helpers and
> the use of GDB's "varobj" mechanism to create displayed data which is
> clumsy to use for non-trivial displays, causes lots of frontend<->GDB
> roundtrips for bigger structures and which is the main obstacle for further
> cross-backend re-use of code, with the obvious consequences for both
> maintenance and feature development.
> 
> Right now I believe this does not affect anyone really badly anymore.
> 
Well unfortunatly lots of cross compilers for Winblows like e.g. this one
https://launchpad.net/gcc-arm-embedded
don't have Python enabled. I think the reason is that nativly compiling gdb is 
no fun on Windows and cross compiling with Python support is pretty  
complicated. I failed in my attempts to cross compile gdb with Pyhton enabled.
I know its possible -as Qt has an gdb with Python enabled- but unfortunatly 
building it, is not so straight forward as one would like.

So the baremetal stuff would be affected by this change.

Best regards
Tim
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to