Re: OT: Re: Is it possible to statically link python into gdb?

On Wed, Jun 25, 2014 at 4:32 PM, Tim Sander <[email protected]> wrote:
> Hi Terry
>> Very appreciate your help. Indeed the python that is statically linked
>> into gdb needs other modules to run correctly. I now worked around
>> this issue by following steps:
>>
>> 1). build and install python 2.7 in dynamic way (produced the
>> libpython2.7.so instead of libpython2.7.a). This python is installed
>> to my own path instead of system path.
>> 2). unset the variable PYTHONHOME and then export
>> PYTHONHOME=MY-OWN-PATH:/usr, then configure, build and install gdb.
>> 3). now copy the gdb to other machine, everything works fine. The only
>> requirement is user will need to install libpython2.7 in their
>> machine.
>>
>> I admit that I have to make a compromise here. I am delivering gdb to
>> my customer and my expectation is that they can use my gdb with python
>> support no matter there is python in their system and no matter the
>> version of their installed python. After a lot of attempts, I think I
>> can't reach my expectation. I guess I have to live with my above
>> workaround.
> Its good you found a workable solution.
>
> I think i have seen your name on the
> https://launchpad.net/gcc-arm-embedded? Is your work on this related? It would
> be really nice to have a python enabled gdb in this toolchain.
>
> I am working on the baremetal plugin for qtcreator. With 3.1, qtcreator has a
> dependecy on a python enabled gdb. It would be really great if there would be
> a ready to use toolchain for this to use for embedded development with
> qtcreator.
>
> Best regards
> Tim

You are right. It's me. Hopefully we will enable this feature in
upcoming 4.9 based release.

BR,
Terry