On Mon, Jan 6, 2014 at 12:01 PM, Tim Sander <[email protected]> wrote:
> 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. > You might want to check out dist/gdb/Makefile.mingw in qt-creator repo. All you need is msys environment with gcc, wget and unzip. Change the "targets" line to your needs, and make -f Makefile.mingw. - Orgad
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
