From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13937 invoked by alias); 17 Jan 2011 22:59:53 -0000 Received: (qmail 13918 invoked by uid 22791); 17 Jan 2011 22:59:52 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 17 Jan 2011 22:59:47 +0000 Received: (qmail 3595 invoked from network); 17 Jan 2011 22:59:45 -0000 Received: from unknown (HELO ?192.168.1.143?) (yao@127.0.0.2) by mail.codesourcery.com with ESMTPA; 17 Jan 2011 22:59:45 -0000 Message-ID: <4D34C9DE.3040603@codesourcery.com> Date: Tue, 18 Jan 2011 00:42:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Tom Tromey CC: gdb-patches@sourceware.org Subject: Re: [rfa/rfc] Build libcommon.a for gdb and gdbserver References: <4D30E23F.3080103@codesourcery.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-01/txt/msg00372.txt.bz2 On 01/17/2011 10:05 AM, Tom Tromey wrote: > Yao> In order to achieve that, configure.ac and Makefile.in will be > Yao> created in common/ dir. > > Is there a way we can avoid this? Each configure carries some weight: > more maintenance (especially if they must be fixed in parallel), more > size, and slower build speeds. I am a little bit reluctant about adding configure.ac/Makefile.in as well, :) We have to add different objects in libcommon.a varies on different targets, and seems only configure/Makefile helps on this. I can't figure out any alternatives to this in my mind so far. > I see that common/Makefile.in doesn't have automatic dependency > tracking. I think it should, especially if we are planning to move more > and more code there. This would be simpler with a single configure:-) I'll fix that. -- Yao Qi