X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <19171449 DOT post AT talk DOT nabble DOT com> Subject: RE: Symlink resolving Date: Tue, 26 Aug 2008 23:59:07 +0100 Message-ID: <07fa01c907cf$5857e5f0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <19171449.post@talk.nabble.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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 prokash wrote on 26 August 2008 23:14: > All: > > How to resolve symlink in an archive ( tarr'd ) so that when I use windows > visual studio or other IDE the include and other references are in tact... Well, windows doesn't do symlinks by itself, so really your best bet would be if you could create the archive using the "--dereference" option in the first place, so that you get just real physical copies of the linked files when you unpack it. If it's an existing archive, you could use cygwin to unpack it, then repack it using that option. Oh, and please! Don't send empty replies to spam posts. That's really irritating. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/