X-Spam-Check-By: sourceware.org Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Re: Does 'ar' work with native MS Windows libs? Date: Tue, 3 Oct 2006 15:48:55 -0400 Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F7B1302@PAUMAILU03.ags.agere.com> In-Reply-To: From: "Williams, Gerald S \(Jerry\)" To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k93K1tn6021964 Coatimundi wrote: > If paths are included in the archive (which is typical for > libs created by Visual Studio), then ar may in some cases > claim that members (displayed with 'ar t') do not exist > when doing "ar x lib.a {object}" either by path/name.obj > or just name.obj. I think you need to use the -P option: $ ar t foobar.lib release\foo.obj release\bar.obj $ ar xv foobar.lib 'release\foo.obj' no entry release\foo.obj in archive $ ar xvP foobar.lib 'release\foo.obj' x - release\foo.obj gsw -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/