Re: AW: AW: Building insight independantly of gdb

[Keith Seitz <keiths at redhat dot com>]

Michael Stather wrote:
> Well I did *g Sorry, I just hit "reply"
> So is it possible to install insight but not the included gdb?I mean with
> configure switches?

There is no way to do this with configure flags. That leaves you two 
options:

1) Copy /usr/local/bin/gdb; install insight; clobber newly-installed gdb 
with copy
2) Specify --prefix=$INSTALLDIR to configure, build, install, remove 
$INSTALLDIR/bin/gdb, then copy the contents to /usr/local. (Or simply 
use the new installdir and add that path to the end of your current PATH.)

Keith

> -----Ursprüngliche Nachricht-----
> Von: Keith Seitz [mailto:keiths@redhat.com] 
> Gesendet: Samstag, 19. November 2005 17:58
> An: Michael Stather
> Betreff: Re: AW: Building insight independantly of gdb
>
> Please post to the mailing list for the benefit of others.
>
> Keith
>
> Michael Stather wrote:
>
> > Thanks for the explanation.
> > I´ve a SuSE system where gdb is installed as a rpm package. And I 
> > use/test several IDEs which use GDB as a debugger.
> > So I don´t want insight to interfere with my gdb installation. I like 
> > to use it as a "seperate" program which uses it´s included gdb while 
> > other apps which request gdb use the installed one.
> > The thing with the path doesn´t work since /usr/local/bin appears 
> > before /usr/bin (where my installed gdb is) Can I configure switches 
> > (or whatever) to have insight compiled without installing gdb (but 
> > still using it). This would IMHO be the only possibility to install 
> > insight without interferring an installed gdb?
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Keith Seitz [mailto:keiths@redhat.com]
> > Gesendet: Samstag, 19. November 2005 17:22
> > An: Michael Stather
> > Cc: insight@sources.redhat.com
> > Betreff: Re: Building insight independantly of gdb
> >
> > Michael Stather wrote:
> >
> >
> > > As I read from the "about" page insight is a GUI for gdb. But it seems 
> > > to be built as a "gdb" executable mixing native gdb functionality with 
> > > a
> >
> > gui.
> >
> > Unlike ddd, eclipse, and many other guis for gdb, Insight *is* gdb. 
> > They are the same executable. This means that insight is orders of 
> > magnitude faster than the rest.
> >
> >
> >
> > > But if insight replaces my existing gdb other gdb GUIs and apps which 
> > > use gdb don´t work anymore.
> > > Can I compile insight independant from gdb, so that it doesn´t 
> > > interfere with an existing gdb installation. The actual executable 
> > > should be named "insight" then.
> >
> >
> > When you build gdb/insight, you get two executables: "gdb" and "insight".
> > Both are identical except that one defaults to starting up the GUI 
> > (insight) and one does not.
> >
> > Other than file size, the presence of the insight code in the gdb 
> > executable does not alter the gdb executable: you basically still have a
> >  gdb release, compatible (if not identical) with any release of gdb 
> > with the same version.
> >
> > If you require to keep some other version of gdb, simply don't install 
> > the one that is built with insight. Only install the insight executable.
> > [In practice, its probably easiest to install both executables into, 
> > e.g., /usr/local, and put your other gdb into. e.g., /usr/bin. Setting 
> > your PATH will then grab the right one at the right time.]
> >
> > Although I admit, I find this a bit weird. Are you saying that you 
> > want to use different versions of gdb, one when running the command 
> > line (or some other spawn-gdb GUI) and one when running insight?