X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4BB1FA4C.5070107@gmail.com> Date: Tue, 30 Mar 2010 14:19:08 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: concurrents versions of cygwin References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 On 30/03/2010 10:18, David BONNIN wrote: > It seems, that eclipse+CDT look in windows registry to find cygwin to > compile. It's going to be possible to override that in the next version of Eclipse (3.6 Helios) by setting your PATH so that the toolchain you want to find is first when you launch Eclipse. Will only work reliably with 1.7 I think, but you could have a go and see if your toolchains run OK against a 1.7 DLL, you might be OK. (Otherwise, it might yet be possible to fix the CDT before release. Eclipse Bug #213920, and, as others have mentioned, please take any further discussion to the cdt-dev mailing list.) cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple