From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2479 invoked by alias); 19 Nov 2005 18:04:50 -0000 Received: (qmail 2466 invoked by uid 22791); 19 Nov 2005 18:04:50 -0000 X-Spam-Check-By: sourceware.org Received: from h8391.serverkompetenz.net (HELO h8391.serverkompetenz.net) (81.169.185.180) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 19 Nov 2005 18:04:49 +0000 Received: from kyromaster (p54ADCA14.dip.t-dialin.net [84.173.202.20]) by h8391.serverkompetenz.net (Postfix) with ESMTP id 72A7351819E for ; Sat, 19 Nov 2005 18:56:07 +0100 (CET) From: "Michael Stather" To: Subject: AW: AW: AW: Building insight independantly of gdb Date: Sat, 19 Nov 2005 20:46:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable In-Reply-To: <437F68A0.4020406@redhat.com> Message-Id: <20051119175607.72A7351819E@h8391.serverkompetenz.net> X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2005-q4/txt/msg00030.txt.bz2 Sorry, I submitted it as bug #282=20 -----Urspr=FCngliche Nachricht----- Von: Keith Seitz [mailto:keiths@redhat.com]=20 Gesendet: Samstag, 19. November 2005 19:02 An: Michael Stather Cc: insight@sources.redhat.com Betreff: Re: AW: AW: Building insight independantly of gdb 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=20 > 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=3D$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=FCngliche 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 >=20 > Please post to the mailing list for the benefit of others. >=20 > Keith >=20 > Michael Stather wrote: >=20 >>Thanks for the explanation. >>I=B4ve a SuSE system where gdb is installed as a rpm package. And I=20 >>use/test several IDEs which use GDB as a debugger. >>So I don=B4t want insight to interfere with my gdb installation. I like=20 >>to use it as a "seperate" program which uses it=B4s included gdb while=20 >>other apps which request gdb use the installed one. >>The thing with the path doesn=B4t work since /usr/local/bin appears=20 >>before /usr/bin (where my installed gdb is) Can I configure switches=20 >>(or whatever) to have insight compiled without installing gdb (but=20 >>still using it). This would IMHO be the only possibility to install=20 >>insight without interferring an installed gdb? >> >>-----Urspr=FCngliche 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=20 >>>seems to be built as a "gdb" executable mixing native gdb=20 >>>functionality with a >> >>gui. >> >>Unlike ddd, eclipse, and many other guis for gdb, Insight *is* gdb.=20 >>They are the same executable. This means that insight is orders of=20 >>magnitude faster than the rest. >> >> >> >>>But if insight replaces my existing gdb other gdb GUIs and apps which=20 >>>use gdb don=B4t work anymore. >>>Can I compile insight independant from gdb, so that it doesn=B4t=20 >>>interfere with an existing gdb installation. The actual executable=20 >>>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=20 >>executable does not alter the gdb executable: you basically still have=20 >>a >> gdb release, compatible (if not identical) with any release of gdb=20 >>with the same version. >> >>If you require to keep some other version of gdb, simply don't install=20 >>the one that is built with insight. Only install the insight executable. >>[In practice, its probably easiest to install both executables into,=20 >>e.g., /usr/local, and put your other gdb into. e.g., /usr/bin. Setting=20 >>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=20 >>want to use different versions of gdb, one when running the command=20 >>line (or some other spawn-gdb GUI) and one when running insight? >>