From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5760 invoked by alias); 7 Feb 2003 03:59:35 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 5753 invoked from network); 7 Feb 2003 03:59:35 -0000 Received: from unknown (HELO mx1.redhat.com) (172.16.49.200) by 172.16.49.205 with SMTP; 7 Feb 2003 03:59:35 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h173xZf13345 for ; Thu, 6 Feb 2003 22:59:35 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h173xZa19869 for ; Thu, 6 Feb 2003 22:59:35 -0500 Received: from [150.1.200.14] (vpn50-26.rdu.redhat.com [172.16.50.26]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h173xYB29101; Thu, 6 Feb 2003 22:59:34 -0500 Subject: Re: [RFC] Remove tcl/tk/itcl/itk dependencies from Makefile.in From: Keith Seitz To: Chris Faylor Cc: "insight@sources.redhat.com" In-Reply-To: <20030207032337.GA29239@redhat.com> References: <20030207032337.GA29239@redhat.com> Content-Type: text/plain Organization: Message-Id: <1044590630.1492.15.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Fri, 07 Feb 2003 03:59:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00088.txt.bz2 On Thu, 2003-02-06 at 19:23, Christopher Faylor wrote: > Anyway, I've managed to build a version of gdb by removing TCL_DEPS, > TK_DEPS, ITCL_DEPS, and ITK_DEPS from the Makefile and I can kludge > something for my cygwin build system so that I can make this automatic. > I was just wondering if anyone would mind eliminating these > dependencies. You've built insight using "standard", installed versions of Tcl, Tk, Itcl? THAT'S WONDERFUL! > So, the question is: Is it ok to remove the tcl/tk/itcl/itk *_DEPS files > from the gdb Makefile? This would also be a step in the direction of > allowing insight to be built from system tcl/tk libraries. Well, here's the idea I had in mind... We would like to support two building methodologies. One where we are using the tcl, tk, etc from the build tree and one where we use the installed versions. If we're building with the installed versions, there should be no dependency (obviously). If we're building tcl et al, then we should have the dependency. I believe that this can be done easily enough. My rough outline of the process looks something like: if --with-*config and it exists, use it. If not, assume build tree. If --with-tclconfig was specified and it exists, use that directory to search for *config.sh, too. Same for --with-tcl-headers and --with-tcl-library. I think this is what the likes of BLT use, and it seems a reasonable (if lengthy) approach. Of course, as you observe, there is a ton of hacking to do at gdb's m4 files. I was actually planning to do this some day, when I get back to finishing the gdb/Insight split and we have our own configury and Makefiles, but, well, that never seems to happen. I know.. I'm a bad maintainer. Anyway, not to discourage, I think that I would check if I could find a suitable Tcl, Tk, etc in the build tree and then set TCL_DEPS and TK_DEPS accordingly, even if the --with-* stuff isn't in yet. Does this sound like a reasonably way to inch forward? Keith