From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8754 invoked by alias); 25 Mar 2002 23:40:49 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 8741 invoked from network); 25 Mar 2002 23:40:48 -0000 Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35) by sources.redhat.com with SMTP; 25 Mar 2002 23:40:48 -0000 Received: by zwingli.cygnus.com (Postfix, from userid 442) id 127345EA11; Mon, 25 Mar 2002 18:40:47 -0500 (EST) From: Jim Blandy To: gcc@gcc.gnu.org Cc: gdb@sources.redhat.com Subject: sharing libcpp between GDB and GCC Message-Id: <20020325234047.127345EA11@zwingli.cygnus.com> Date: Mon, 25 Mar 2002 15:40:00 -0000 X-SW-Source: 2002-03/txt/msg00235.txt.bz2 At the moment, libcpp lives in the `gcc' directory of its source tree, and it shares GCC's makefile and configure script. I assume there's general agreement that, if GDB and GCC are going to share libcpp, we'll want to pull libcpp out into its own top-level directory, with its own makefile and configure script, and move its header files into the top-level #include directory. Is that so? There are two approaches we could take; I'm not sure which is best. - The GCC folks could do this extraction, ensuring that GCC continues to work. Then we can copy that directory over into GDB's repository, and begin the libcpp/GDB integration. - Or, the GDB folks could make their own libcpp directory and drop my simple-minded expander into it, along with its header file, ensuring that GDB continues to work. Then, we wipe that out and replace it with libcpp, and do the libcpp/GDB integration as part of the same commit. I think I prefer the former. In the latter case, one has to do the simple-minded-to-libcpp replacement simultaneously with the libcpp/GDB adaptation, or else GDB will cease to work. In the former case, we can have libcpp sitting in GDB's repository, while GDB continues to use the simple-minded expander, and do the libcpp/GDB reconciliation (whatever is necessary) as a separate step. Are the GCC folks willing to tackle this? Do you agree that this seems to be the next logical step? (I've got some weird reverse-caffeine headache or something, so if this is totally stupid, please be kind.)