Re: r147958 - in /trunk/libstdc++-v3: ChangeLog Mak...

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Joseph" == Joseph S Myers <joseph@codesourcery.com> writes:

Joseph> There is no particular reason for the pretty printers to need
Joseph> to be part of the target's filesystem when they are only
Joseph> needed on the host, but if they are not then they need
Joseph> locating relative to the debugger not to the filesystem
Joseph> containing the library.

I think it is best to consider all the python code as a unit.  That is
because the pretty-printers are specific to a particular version of
libstdc++.

So, if you set up a sysroot and want this pretty-printing support, you
should make sure all the code is in the sysroot.  And, the sysroot has
to have the same relative directory layout as specified when the
target system's libstdc++ was configured.

I guess this is less than ideal in the case where you want to make a
minimal sysroot.  But, we aren't talking about much data here, all the
Python code is 22k.  And, this whole mechanism is really just a user
convenience.  In an extreme case you can also use gdb commands to load
the pretty-printers manually.

Tom