Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Authentication-Warning: eos.vss.fsi.com: ford owned process doing -bs Date: Thu, 3 Apr 2003 14:49:09 -0600 (CST) From: Brian Ford X-X-Sender: ford AT eos To: cygwin AT cygwin DOT com Subject: Installing CVS built cygwin? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Elaborating on my previous question: > How do you developers manage to test run Cygwin versions and then > revert? Obvioulsy, for things like the new 64 bit support, just > swapping cygwin1.dll is not sufficient. I thought I would try the following: install into a temp dir in temp dir do: find . ! -type d > .../cygfilelist in /usr do: tar jcvf .../cygreleased.tar.bz2 -I .../cygfilelist stop all Cygwin processes to install, in /usr do: tar cf - -C temp_dir . | tar xvf - to uninstall, in /usr do: for file in `cat .../cygfilelist`; do rm -f $file; done tar jxvf .../cygreleased.tar.bz2 Questions: I noticed that the new include files would be installed in /usr/i686-pc-cygwin/include and the new libs in /usri686-pc-cygwin/lib. I think I remember this overrides includes in /usr/include and libs in /usr/lib, but what about gcc's fixed includes? There must be a simpler way... Thanks for any tips. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/